Mark Rowe 30e58022cf Include property names in type error exceptions thrown by Realm.create (#1069) ...

* Add and adopt `Value::is_binary` / `Value::to_binary` / `Value::from_binary`.

These methods allow conversions between `BinaryData` and the equivalent
JavaScript types without using `NativeAccessor`. Instead,
`NativeAccessor` now itself delegates to these methods.

* Have `NativeAccessor::value_for_property` and `RealmObjectClass::set_property`
verify that values are valid for the property in question.

If not, we throw an exception that includes the name and type of the
property in question.

`NativeAccessor` is changed to always hold a reference to a `Realm` and
an `ObjectSchema` in order to make this validation possible.

* Fix the Windows build.

* Remove an unused, incorrect forward declaration of a template class
  named `Realm` that caused ambiguity with object store's `Realm` class.
* Disambiguate between `realm::js::PropertyType` and
  `realm::PropertyType`.

* Update CHANGELOG.md

2017-06-20 14:40:01 +02:00

..

android

Include property names in type error exceptions thrown by Realm.create (#1069)

2017-06-20 14:40:01 +02:00

ios

Support the new React Native C++ bridge (#1065)

2017-06-14 14:44:28 +02:00

.eslintrc.json

Properly configure ESLint for syntax checking

2016-03-16 13:01:38 -07:00

.npmignore

NPM ignore react-native/android folder

2016-02-11 16:55:36 -08:00

index.js

Fix ListView imports for React Native 0.25

2016-05-16 13:23:19 -07:00

listview.js

Fix ListView imports for React Native 0.25

2016-05-16 13:23:19 -07:00