ec87281cc1
don't convert undefined to null in rpc requests
2015-10-27 12:13:57 -07:00
18d65471be
fix and tests for setting null properties
2015-10-27 12:13:57 -07:00
ac1cdfdc8b
support null for basic propety types
2015-10-27 12:13:57 -07:00
e3fb40f299
enable nullable propeties without a macro
2015-10-27 12:13:57 -07:00
fc631c3e6f
wont work until we have propery object store support
2015-10-27 12:13:57 -07:00
0df214ad21
Merge pull request #101 from realm/sk-object-getters
...
Non-existent object getters shouldn't throw exceptions
2015-10-27 11:09:21 -07:00
db67fe71ea
only ignore invalid property exceptions
2015-10-27 09:39:52 -07:00
9092f9ac5f
use typed exceptions
2015-10-27 09:39:52 -07:00
0511bade62
Non-existent object getters shouldn't throw exceptions
2015-10-27 09:39:52 -07:00
8e1eb661c5
Merge pull request #100 from realm/al-notification
...
improve notification api
2015-10-27 07:56:37 -07:00
a1c4cd5702
pr fixes
2015-10-27 07:48:11 -07:00
6f41c3cf68
take notification name
2015-10-26 19:18:24 -07:00
bb68e45250
support notifications in chrome
2015-10-26 16:49:46 -07:00
6f57500972
change notification name to change
2015-10-26 16:19:12 -07:00
246ccc7bde
add other notification methods
2015-10-26 16:15:46 -07:00
ab1965c27e
no more notification token
2015-10-26 16:03:32 -07:00
6db449ef06
Merge pull request #99 from realm/al-os
...
Object store cleanup
2015-10-26 15:39:37 -07:00
b7d47ac543
apply newest object store changes
2015-10-26 15:27:43 -07:00
9cfcc2ea9e
Fix for running RealmReactTests in release mode
...
The RTCDevMenu is missing the `moduleName` class method in release mode.
2015-10-26 14:57:50 -07:00
32ebd7f218
Remove RCTTest linkage from ReactTests and ReactExample
...
This module has build errors with Release configuration and is not necessary. When in Chrome debugging mode, a warning will be issued about missing the RCTSnapshot module though, which is why we linked against it in the first place.
2015-10-26 14:57:06 -07:00
ed193d8f5c
make list members private
2015-10-26 13:32:29 -07:00
a2cd949e09
Prevent tests from ever opening Chrome
...
The test is commented out for now.
2015-10-26 13:25:15 -07:00
c9ef337552
make object members private
2015-10-26 13:24:27 -07:00
31819a5ee6
Merge commit '347145b4f1c40409c68af0ad61be15ee5f9d04f2' into al-os
2015-10-26 12:52:20 -07:00
6d4b8d1e7b
Merge pull request #96 from realm/sk-realmjs-api
...
Change RealmJS to provide a C API
2015-10-26 12:08:42 -07:00
d3cf748dc1
Rename RealmRPC.mm -> RealmRPC.cpp
2015-10-26 01:20:14 -07:00
0843d69a4f
Expose RealmJS API as C functions
...
We're still using Objective-C to delete test files, so we can't rename the implementation file quite yet.
2015-10-26 01:14:33 -07:00
4d73c13466
Merge branch 'sk-chrome-xcode-tests'
...
* sk-chrome-xcode-tests:
Actually report test failures when running in Chrome
Change RealmReactTests to run with both executors
Fix RealmReactTests to work through Chrome
Use a default to override Chrome debugging setting
Change ReactTests project to 4 space indentation
2015-10-23 16:38:17 -07:00
1ede355b78
Actually report test failures when running in Chrome
...
Turns out Chrome doesn't report back exceptions, but instead does pass back an array of five empty arrays (I am not kidding).
2015-10-23 14:13:38 -07:00
e7b05d2dc6
Change RealmReactTests to run with both executors
...
A new approach was needed for this. The RCTDevMenu is disabled so that it doesn't interfere with us changing the executor class. A suffix is added to the name of test cases that are run in Chrome.
2015-10-23 14:12:35 -07:00
ad47da8c09
Merge pull request #93 from realm/al-rpc-cpp
...
Rewrite rpc server in c++ so it can be used on android
2015-10-22 18:10:21 -07:00
28e21041bc
bugfix and move gcd out of rpc
2015-10-22 18:06:11 -07:00
8b5a8a731c
fix naming
2015-10-22 17:59:05 -07:00
c3c9cee0ee
make it work
2015-10-22 16:49:32 -07:00
92a9113ef6
get it to compile
2015-10-22 15:31:26 -07:00
418d6dfc1c
partial port of rpc server to cpp
2015-10-22 10:44:10 -07:00
33edd04897
Merge pull request #89 from realm/al-null
...
Test/fix setting all primitive types to null/undefined
2015-10-22 06:24:08 -07:00
2fe1f0d26e
Fix RealmReactTests to work through Chrome
...
The key idea was the cycle the runloop once after receiving the RCTJavaScriptDidLoadNotification so that the RCTDevMenu could also handle that notification and setup the bridge properly, as well as not block the main thread by spinning the runloop instead.
2015-10-22 02:49:15 -07:00
6a8fa75a37
Use a default to override Chrome debugging setting
...
This is done in a way that does not override the persistent user defaults. You set this default when launching the app by supplying `-RealmReactEnableChromeDebugging YES/NO` launch arguments.
2015-10-22 02:47:10 -07:00
56ad4faa19
Change ReactTests project to 4 space indentation
...
Also changed copyright notice.
2015-10-22 02:34:46 -07:00
6c3bfef73d
Merge pull request #90 from realm/al-cordova-update
...
Update version/Fix cordova example
2015-10-21 23:07:42 -07:00
1be81205d0
check for undefined was already covered
2015-10-21 23:06:39 -07:00
ac544205a1
test setting all primitive types to null/undefined throw
2015-10-21 23:06:39 -07:00
ce682c3f70
Merge pull request #88 from realm/al-project
...
Make ReactTests runnable from RealmJS project
2015-10-21 23:05:04 -07:00
a94e14cb70
update cordova to latest version/fixex
2015-10-21 20:52:18 -07:00
08a84bd8e9
cleanup scheme and target names
2015-10-21 19:20:45 -07:00
5d78670802
make ReactTests a subproject of RealmJS
2015-10-21 19:17:22 -07:00
290a595259
update to latest core
2015-10-21 19:12:36 -07:00
9cbc695fd7
Skip throwing an exception inside ResultsSetProperty
2015-10-21 15:59:11 -07:00
bd2d1559d1
Error when assigning to Result index or length
...
Added some tests. Turns out our Chrome layer already did this too, so no changes were needed there.
Resolves #70
2015-10-21 15:25:53 -07:00
Ari Lazier
Scott Kyle