-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
Dispatch commands to both UIManagers from both renderers #17211
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this going to cause any early require problems such as both UI managers eagerly instantiating or is that all fixed?
Since it is accessing the fabricUIManager directly from the global we shouldn't have any of those problems. When I forgot to do that and instead defined it at the top of the file, the tests failed. So I think this should be safe. |
…ebook#17211)" This reverts commit 8eee0eb.
…ebook#17211)" (facebook#17232) This reverts commit 8eee0eb.
…ebook#17211)" (facebook#17232) This reverts commit 8eee0eb.
…ers (facebook#17211)" (facebook#17232)" This reverts commit d0fc0ba.
…ers (facebook#17211)" (facebook#17232)" (facebook#17799) * Revert "Revert "Dispatch commands to both UIManagers from both renderers (facebook#17211)" (facebook#17232)" This reverts commit d0fc0ba. * Clean up another __DEV__ warning check
ReactNative's internal module for
codegenNativeCommands
needs to dispatch to Fabric or paper depending on the node it was passed.This makes the internal Renderer's exported
dispatchCommand
method both support components created with either renderer.There was a test file
ReactFabricAndNative-test.internal.js
that tests components created with Fabric passed to the Paper renderer.