useAnchorRef: update deprecation message #45302
Merged
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
ciampo
added
[Type] Developer Documentation
|
Size Change: -10 B (0%) Total Size: 1.28 MB
ℹ️ View Unchanged
|
ciampo
added
the
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.
What?
Following the conversation in #45195, update the deprecation message for the
useAnchorRef— the hook will not be deleted as of WordPress 6.3.Why?
To better adhere to the deprecation policies of the WordPress project. See the conversation in #45195 for more details.
How?
Update changelog and remove 6.3 version from the deprecation warning.
✍️ Dev Note
As also written in an update to the previous "Editor Components updates in WordPress 6.1" post, the deprecated
useAnchorRefhook from the@wordpress/rich-textpackage will not be deleted in WordPress 6.3, as initially planned.