Cover react/renderer/dom with Stable API guards - #57961
Open
j-piasecki wants to merge 2 commits into
Open
Conversation
Differential Revision: D109847184
Summary: Classifies `react/renderer/dom` as a private target under the three-tier C++ stable API visibility model. `DOM.h` now includes `<react/cxxstableapi/PrivateGuard.h>`. Consumers that opt into `RN_STRICT_API` now get an error if they include `DOM.h` directly; without that flag the guard is inert, so no existing build changes behaviour. Changelog: [Internal] Differential Revision: D116013879
|
@j-piasecki has exported this pull request. If you are a Meta employee, you can view the originating Diff in D116013879. |
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:
Classifies
react/renderer/domas a private target under the three-tier C++ stable API visibility model.DOM.hnow includes<react/cxxstableapi/PrivateGuard.h>. Consumers that opt intoRN_STRICT_APInow get an error if they includeDOM.hdirectly; without that flag the guard is inert, so no existing build changes behaviour.Changelog: [Internal]
Differential Revision: D116013879