Commit Graph

6 Commits

Author SHA1 Message Date
astigsen 5186eeb84e Add Object.linkingObjectCount() 2018-05-15 14:31:54 +02:00
James Stone 591aa9fee7 Initial work for unnamed backlink queries and @links.@count tests 2018-04-10 16:37:41 -07:00
James Stone 497de5f3ea Fix named linking object queries across classes (#1734)
* Fix named linking object queries across classes
* Add change log entry, remove debug code
2018-04-03 11:48:33 +02:00
James Stone bd5c237b0f Named backlink queries working with core 5.3.0 2018-02-19 16:14:10 -08:00
James Stone 6f43324636 Preliminary work for queries over named backlinks 2018-02-13 16:17:27 -08:00
Marius Rackwitz 9e0a9a3bd3 Add support for accessing linking objects / backlinks (#1101)
* 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
2017-06-29 11:59:10 +02:00