You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the native bridge is 1) very simple (lump modules) 2) boilerplate heavy (macros/wrappers for desired exports, objects/data needing JSONification) 3) limited to Obj-C (or Swift wrapped/de-typed in Obj-C)
#1 and #2 could be solved by supporting the native JavaScriptCore JSExport protocol functionality, so that arbitrary Obj-C objects are passable to/interactable from JS land. If this is possible as a short term measure, it would be very valuable.
But I imagine a fine grained, full, automatic bridge unique to RN could be (and would need to be, to provide the same functionality for Android) developed in the longer term, given the skill/knowledge base that participates in this project.
I'm imagining, for example, a native bridge between JS<->Obj-C, TS<->Swift that's code-gen'd for full support of each's interfaces/lang features. Has something like this ever been played with?
The text was updated successfully, but these errors were encountered:
If you are looking to invoke native code synchronously from JS, the CxxBridge modules support this.
JSExport wouldn't work on Android and it doesn't go through the JS bridge so it's a bit of a non-starter but for your own projects you can get the JSCExecutor from the CxxBridge (need a private category) and the JSContext from that. If you call RN functions from code invoked by JSContext, they might get scheduled outside the RN event loop and cause bugs, so be very careful.
It doesn't make sense for RN to support this nor encourage it, the pitfalls are non-obvious.
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
Currently the native bridge is 1) very simple (lump modules) 2) boilerplate heavy (macros/wrappers for desired exports, objects/data needing JSONification) 3) limited to Obj-C (or Swift wrapped/de-typed in Obj-C)
#1 and #2 could be solved by supporting the native JavaScriptCore JSExport protocol functionality, so that arbitrary Obj-C objects are passable to/interactable from JS land. If this is possible as a short term measure, it would be very valuable.
But I imagine a fine grained, full, automatic bridge unique to RN could be (and would need to be, to provide the same functionality for Android) developed in the longer term, given the skill/knowledge base that participates in this project.
I'm imagining, for example, a native bridge between JS<->Obj-C, TS<->Swift that's code-gen'd for full support of each's interfaces/lang features. Has something like this ever been played with?
The text was updated successfully, but these errors were encountered: