Restore listing creation in the V1 REST API - #2951
Open
RabbiIslamRony wants to merge 1 commit into
Open
Conversation
Member
Author
|
The reported PHPCS failure occurs in the inherited |
Member
Author
|
A focused LocalWP retest against the current PR head also passed the taxonomy adapter path: an authenticated V1 POST with a valid directory and category returned HTTP 201, included the V1 listing Location header, and created the expected listing. The temporary listing and application password were removed after the check. |
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
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.
PR Type
What kind of change does this PR introduce?
Description
How to reproduce the issue or how to test the changes
name=my_new_listingto/wp-json/directorist/v1/listings.Locationheader.directoryand confirm the default directory is used. Then supply invalid directory and taxonomy IDs and confirm HTTP 400 responses.The V1 controller now adapts its documented flat schema to the current builder-aware submission service. Existing attachment IDs require image and edit checks, taxonomy terms are validated against their taxonomy and directory, and V2 remains unchanged.
Any linked issues
Fixes #1133
Checklist