[WIP] Use post_name for query instead of ID #42778
Closed
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.
This is not RfR
What?
Amends the REST API to accept a string based slug when querying for a single
wp_navigation
post.Why?
See #38291 (comment).
Essentially we need the REST API to be able to find a given
wp_navigation
by a slug rather than a post ID. This will ultimately make Navigations more portable across different installs.Follows a similar path to the Template Parts API.
How?
Amends the
rest_controller_class
for handlingwp_navigation
to a custom controllerGutenberg_REST_Navigation_Controller
. This then overides theget_post
method of the parent classes so that it queries bypost_name
(slug).It also registers a new GET route which allows for using a string as the ID.
Testing Instructions
http://localhost:8888/wp-json/wp/v2/navigation/{{POST_NAME_SLUG_OF_YOUR_NAV_POST}}
Screenshots or screencast