Remove changes_available implementation that asserts
This gets called when a Realm changes on another thread, but is called on the correct thread on iOS. It doesn't look like it will be called on Android, so we can unofficially support iOS accessing Realms from multiple bindings for now. Fixes #352
This commit is contained in:
parent
858380b86e
commit
0f9f450062
|
@ -36,9 +36,6 @@ using RJSAccessor = realm::NativeAccessor<JSValueRef, JSContextRef>;
|
||||||
|
|
||||||
class RJSRealmDelegate : public BindingContext {
|
class RJSRealmDelegate : public BindingContext {
|
||||||
public:
|
public:
|
||||||
virtual void changes_available() {
|
|
||||||
assert(0);
|
|
||||||
}
|
|
||||||
virtual void did_change(std::vector<ObserverState> const& observers, std::vector<void*> const& invalidated) {
|
virtual void did_change(std::vector<ObserverState> const& observers, std::vector<void*> const& invalidated) {
|
||||||
notify("change");
|
notify("change");
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue