Upgrade Image visibility to "for frameworks" (#58283) - #58283
Closed
j-piasecki wants to merge 1 commit into
Closed
Conversation
|
@j-piasecki has exported this pull request. If you are a Meta employee, you can view the originating Diff in D118440296. |
Summary: Reclassifies `react/renderer/components/image:image` from public to "for frameworks" under the C++ stable API three-tier visibility model. Consumers that opt into `RN_STRICT_API` now get a suppressible warning where they previously got an error pointing at the umbrella, and can acknowledge it with `RN_ALLOW_FRAMEWORKS`; without that flag the guards are inert, so no existing build changes behaviour. Changelog: [Internal] Reviewed By: christophpurrer Differential Revision: D118440296
j-piasecki
force-pushed
the
export-D118440296
branch
from
September 3, 2026 07:52
167cdf3 to
d912a09
Compare
j-piasecki
added a commit
to j-piasecki/react-native
that referenced
this pull request
Sep 3, 2026
Summary: Reclassifies `react/renderer/components/image:image` from public to "for frameworks" under the C++ stable API three-tier visibility model. Consumers that opt into `RN_STRICT_API` now get a suppressible warning where they previously got an error pointing at the umbrella, and can acknowledge it with `RN_ALLOW_FRAMEWORKS`; without that flag the guards are inert, so no existing build changes behaviour. Changelog: [Internal] Reviewed By: christophpurrer Differential Revision: D118440296
j-piasecki
force-pushed
the
export-D118440296
branch
from
September 3, 2026 07:52
d912a09 to
61cc7ca
Compare
j-piasecki
added a commit
to j-piasecki/react-native
that referenced
this pull request
Sep 3, 2026
Summary: Reclassifies `react/renderer/components/image:image` from public to "for frameworks" under the C++ stable API three-tier visibility model. Consumers that opt into `RN_STRICT_API` now get a suppressible warning where they previously got an error pointing at the umbrella, and can acknowledge it with `RN_ALLOW_FRAMEWORKS`; without that flag the guards are inert, so no existing build changes behaviour. Changelog: [Internal] Reviewed By: christophpurrer Differential Revision: D118440296
|
This pull request has been merged in d3b7893. |
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:
Reclassifies
react/renderer/components/image:imagefrom public to "for frameworks" under the C++ stable API three-tier visibility model.Consumers that opt into
RN_STRICT_APInow get a suppressible warning where they previously got an error pointing at the umbrella, and can acknowledge it withRN_ALLOW_FRAMEWORKS; without that flag the guards are inert, so no existing build changes behaviour.Changelog: [Internal]
Reviewed By: christophpurrer
Differential Revision: D118440296