Expose unstable_TextAncestorContext API#52368
Closed
huntie wants to merge 1 commit into
Closed
Conversation
facebook-github-bot
added
CLA Signed
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D77141176 |
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D77141176 |
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D77141176 |
Summary: Pull Request resolved: react#52368 Motivated by react-native-community/discussions-and-proposals#893 (comment). Also align naming for internal usages. Changelog: [General][Added] - Expose `unstable_TextAncestorContext` API Reviewed By: NickGerleman Differential Revision: D77141176
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D77141176 |
Contributor
|
This pull request has been merged in 962a7dd. |
Collaborator
|
This pull request was successfully merged by @huntie in 962a7dd When will my fix make it into a release? | How to file a pick request? |
huntie
added
the
JS API stabilization (1.0)
This was referenced May 13, 2026
yaminyassin
pushed a commit
to yaminyassin/react-strict-dom
that referenced
this pull request
May 15, 2026
React Native 0.81 exposed TextAncestorContext as a public API (react/react-native#52368). Switch from the deep import path 'react-native/Libraries/Text/TextAncestor' to the public 'unstable_TextAncestorContext' export. The deep-import target file in React Native exists solely as a backwards-compatibility shim for react-strict-dom — see https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Text/TextAncestor.js which carries a TODO from @huntie to delete it once this cross-repo reference is fixed. Same React Context object, no behavioral change. Test mock updated to match the new import path; old deep-import mock deleted.
yaminyassin
pushed a commit
to yaminyassin/react-strict-dom
that referenced
this pull request
May 28, 2026
React Native 0.81 exposed TextAncestorContext as a public API (react/react-native#52368). Switch from the deep import path 'react-native/Libraries/Text/TextAncestor' to the public 'unstable_TextAncestorContext' export. The deep-import target file in React Native exists solely as a backwards-compatibility shim for react-strict-dom — see https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Text/TextAncestor.js which carries a TODO from @huntie to delete it once this cross-repo reference is fixed. Same React Context object, no behavioral change. Test mock updated to match the new import path; old deep-import mock deleted.
martinbooth
pushed a commit
to react/react-strict-dom
that referenced
this pull request
May 29, 2026
* Use public unstable_TextAncestorContext API React Native 0.81 exposed TextAncestorContext as a public API (react/react-native#52368). Switch from the deep import path 'react-native/Libraries/Text/TextAncestor' to the public 'unstable_TextAncestorContext' export. The deep-import target file in React Native exists solely as a backwards-compatibility shim for react-strict-dom — see https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Text/TextAncestor.js which carries a TODO from @huntie to delete it once this cross-repo reference is fixed. Same React Context object, no behavioral change. Test mock updated to match the new import path; old deep-import mock deleted. * Update benchmark react-native mock for unstable_TextAncestorContext --------- Co-authored-by: Yamin Yassin <Yamin.Yassin+CAG@cagtechhub.com>
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
3 participants
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:
Motivated by react-native-community/discussions-and-proposals#893 (comment).
Also align naming for internal usages.
Also related to necolas/react-native-web#2447.
Changelog:
[General][Added] - Expose
unstable_TextAncestorContextAPIDifferential Revision: D77141176