* 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
* Update OS
* Use the latest sync
* Update objectstore
* Use realm-sync 7.2
* Add files to project
* Use OS submodule with fix
* Fix object store includes in xcode project
* add missing object store file to binding.gyp
* Update OS with fix for the GlobalNotifier
* Add OS files to Android jni
* Use master@ObjectStore
* Update to sync v1.0.0-BETA-6.3.
This requires updating to current object store master to accommodate the
changes to sync error reporting.
* Add some include folder search paths
* Add thread_safe_reference to the RealmJS target
All realm operations for the RPC are now done in their own thread so it can be allowed to block on waiting for callback results. The recursive and multi-threaded nature of this makes it pretty tricky, but it works!
If adb really isn't found (unsure what conditions would cause that to happen), then `false` will be called which will result in that warning message being displayed instead.
Fixes#351
It still only tries localhost for the simulator, but for devices, we now get a list of possible IP addresses to attempt to connect to before throw a more helpful exception.
Resolves#284 and fixes#276