36ffc6c77c
Simplify object schema info returned from RPC
...
Only the property names are needed.
2016-01-05 13:40:57 -08:00
4109c86343
Make Realm object properties enumerable
2015-12-08 03:26:57 -08:00
336ef55c1f
Remove uses of for-of loops in RPC modules
...
The React Native packager does not transform for-of loops, and minification step uses UglifyJS, which does not yet support ES6 syntax.
Fixes #120
2015-11-05 16:10:52 -08:00
46bee3c867
Add beta licenses to Chrome JS modules
2015-10-28 10:37:17 -07:00
2e592bc101
Sprinkle some const inside ES6 JS code
...
React Native 0.13.0 fixes the bug we experienced by using const.
2015-10-21 13:57:34 -07:00
b07aa72a55
Move all constants into a single JS file
2015-10-19 16:19:43 -07:00
1b7653206a
Generalize getting/setting properties through RPC
2015-10-19 15:46:00 -07:00
4c0cc578d5
Generalize calling methods through the RPC
2015-10-19 12:46:31 -07:00
a997ec5be9
Some cleanup of JS
2015-10-08 15:32:14 -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
cb4fea97d4
Fix "const" search and replace
2015-10-07 17:08:31 -07: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
Scott Kyle
Ari Lazier