-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Multi React DOM support #6233
Comments
@aight8 Thank you raising the issue. We don't have a quick fix but we use React Native Navigation on one of our examples. I will bring it up with the team to get some ideas. |
Hi thank you. I made it work by a fork and export Just for clearification of the problem (that we understand each other correctly), the examples uses react-navigation (single React DOM based), I use react-native-navigation (many React DOM based) In the example it's like:
A
So think about, every Root View, Overlay/Modals are total separately rendered React DOM's. This has the following consequences:
Motivation
The easiest way to solve this issue, to let the user provide Realm and Realm.App object. |
Would love to see a solution for this. |
@aight8 and @nicolaosm - wanted to mention that we're also tracking this issue for a similar feature that you might want to 👍 and watch: #6283 |
Realm React v0.8.0 now supports using an existing Realm instance with a |
Problem
I use react-native-navigation, which uses many React DOM's (every Screen is a separate DOM)
Every screen shares a common Wrapper, which initializes Realm, App and optionally the User Context.
The problem is that:
Solution
As result the Realm and Realm.App Object is managed externally and as side effect the code React DOM stays little bit cleaner.
Alternatives
There is no real alternatives. I currently forked realm-js, exported the React Context.Provider, manually add AuthOperationProvider etc.
How important is this improvement for you?
Dealbreaker
Feature would mainly be used with
Atlas Device Sync
The text was updated successfully, but these errors were encountered: