Block editor: Stabilise RecursionProvider and useHasRecursion APIs #58120
Conversation
This file contains 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
mcsf
added
[Type] Code Quality
mcsf
requested review from
ellatrix,
tellthemachines and
ajitbohra
as code owners
|
Size Change: +68 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
32 tasks
Dev noteStabilization of the block editor's RecursionProvider APIContextOriginally implemented as an experimental hook named
As of today, the following core block types use the RecursionProvider API: Changes with WordPress 6.5The API has been promoted to stable, thereby shedding the For more details and a working example, see the component's README.md document.
Backwards compatibilityThe former identifiers — |
mcsf
added
has dev note
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.
Addresses #57672
Promote the
RecursionProvidercomponent and its accompanyinguseHasRecursionhook to stable APIs, as they have been in use for three years now in the form of "experimental" APIs (__experimentalRecursionProviderand__experimentalUseHasRecursion).No changes in behaviour nor breaking changes should occur. Consumers can still access the old
__experimental*names, but that will trigger deprecation notices.