Use Bridging umbrella in generated modules - #58486
Open
coado wants to merge 2 commits into
Open
Conversation
Summary: Expose the Bridging module through a stable public C++ umbrella and enforce that strict API consumers use that supported entry point. Publish the umbrella and guard dependency through the supported build and packaging surfaces. Changelog: [Internal] Differential Revision: D119658007
Summary: Generate TurboModule interfaces using the public Bridging C++ entry point so generated consumers remain compatible with the strict API boundary. Changelog: [Internal] Differential Revision: D119658518
|
@coado has exported this pull request. If you are a Meta employee, you can view the originating Diff in D119658518. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
Generate TurboModule interfaces using the public Bridging C++ entry point so generated consumers remain compatible with the strict API boundary.
Changelog:
[Internal]
Differential Revision: D119658518