afa974ccc6
serialize Results like other types, use common method rpc call for objects()
2015-10-08 11:04:50 -06:00
ed3cf01432
consolidate realm methods, code cleanup/remove some duplication
2015-10-08 10:43:38 -06:00
3c9fb1a323
Fix for setting properties through RPC
2015-10-08 02:00:10 -07:00
ebb400ed41
Support delete and deleteAll from RPC
2015-10-08 01:53:22 -07:00
31fc14d602
Support (de)serialization of objects in RPC
...
Everything is a dictionary with either a `value` key or an `id` key. If it's a value, then it will recursively be (de)serialized.
2015-10-08 01:53:01 -07:00
a9cac20f79
Rework lists to each have their own getters
...
This was necessary for them to each have their own enumerable properties. The React Native ListViewDataSource uses Object.keys() to the indexes.
2015-10-07 21:20:14 -07:00
141ce2cb6d
Pass realmId for all calls to convert() in rpc.js
2015-10-07 18:40:09 -07:00
41ba3b62b8
JS implementation for Results from RPC
2015-10-07 17:08:31 -07:00
f35d83a07d
Account for overridden XMLHttpRequest in rpc module
2015-10-07 17:08:31 -07:00
cb4fea97d4
Fix "const" search and replace
2015-10-07 17:08:31 -07:00
131123ff9a
first end to end rpc call
2015-10-06 14:52:49 -06:00
476b3623bb
partial rpc server implemenation
2015-10-06 13:36:56 -06:00
bf1ecfbb07
Initial concept of JS for Chrome debugging
...
The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node).
The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-01 22:56:47 -07:00
Ari Lazier
Scott Kyle