Stabilise block-navigation-areas endpoint #36391
Closed
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
noisysocks
added
[Type] Bug
noisysocks
requested review from
nerrad,
spacedmonkey and
TimothyBJacobs
as code owners
noisysocks
added
the
Backport to WP 6.7 Beta/RC
|
Size Change: -4 B (0%) Total Size: 1.09 MB
ℹ️ View Unchanged
|
|
Oops, this is a duplicate of #36374! |
noisysocks
deleted the
update/stablise-block-navigation-areas-endpoint
branch
noisysocks
removed
the
Backport to WP 6.7 Beta/RC
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.
Description
Renames
__experimental/block-navigation-areasto/wp/v2/block-navigation-areas. This aligns with how the endpoint is named in Core and means we won't get 404 errors while running the plugin against the latest Core trunk.Checklist:
*.native.jsfiles for terms that need renaming or removal).