* First take on running the tests inside an Electron render process
* Making progress
* Making it possible to override the location of the admin token
* Ignoreing the realm-object-server files
* Fixing a console.log to return a string instead of a boolean
But it should probably be removed entirely
* Making the downloaded ROS log less
* Adjusting comments in the test.sh
* Checking number of windows to determine an Electron crash
* Added a test that triggers garbage collection of ArrayBuffers
* Enabled the ability to run the tests in Electrons main process
* Run tests first in main process and the render
* Added a README.md that documents how Electron tests can be run
* Added a comment on why the garbage-collection test was added.
* Waiting with reading the admin token, until it is actually used
* Disabling the GarbageCollectionTests for now
* Make it possible to assign a List or Results to a List property.
The change made in #1069 to improve error messages when values of
incorrect types were assigned to a given property was being too
narrow in the types it accepted for list properties, allowing only
arrays. Lists and Results are now accepted once more.
* Update CHANGELOG.md
* Add support for linkingObjects
* Test linkingObjects
* Borrow names helper from list tests
* include computed properties when serializing the schema for the RN debugger
* add API docs
* review comments
* Expose admin users to JS (#1100)
The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct.
#1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user.
* [1.8.3] Bump version
* add linkingObjects method to Realm.Object
* changelog
