Repository navigation
Abilities API: Replace the author_slug filter of core/content-query with an author object
#14673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jorgefilipecosta
wants to merge
5
commits into
WordPress:trunk
Choose a base branch
from
jorgefilipecosta:update/content-query-author-object
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+809
−189
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
72e77ad
Abilities API: Return the empty result for an `author_slug` that name…
jorgefilipecosta dca36e5
Abilities API: Replace the `author_slug` filter of `core/content-quer…
jorgefilipecosta 45cb782
Abilities API: Tighten the `author` filter descriptions and tests of …
jorgefilipecosta 00af6c7
Abilities API: Drop the tests that check for the removed `author_slug…
jorgefilipecosta 69a0d16
Abilities API: Document that the `author.id` filter of `core/content-…
jorgefilipecosta File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is not correct for IDs.
WP_Querymatches the author ID saved on the post (thepost_authorcolumn). It does not check if the user exists. If a user is deleted, their posts can keep the old ID, and{ id: <old ID> }still returns them.I think this is good behavior. The output still returns
author.idfor these posts, so the caller can use it as a filter. Let's only fix the comment:Could you also add a test? Create a post with
post_author => REST_TESTS_IMPOSSIBLY_HIGH_NUMBER(like intest_author_object_describes_the_author()), then check that{ id: REST_TESTS_IMPOSSIBLY_HIGH_NUMBER }returns it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @gziolo, thank you. The suggestion was applied, and
test_author_filter_by_id_matches_the_posts_of_a_deleted_user()now checks that{ id: REST_TESTS_IMPOSSIBLY_HIGH_NUMBER }returns the post with that stored author ID.