-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Update build_query_vars_from_query_block to handle new taxQuery structure
#10632
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
ntsekouras
wants to merge
7
commits into
WordPress:trunk
Choose a base branch
from
ntsekouras:update-build_query_vars_from_query_block-tax-query
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.
+149
−10
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
26ce245
Update `build_query_vars_from_query_block` to handle new `taxQuery` s…
ntsekouras 27b130e
add the code and tests
ntsekouras 1855dd3
check for empty `taxQuery` key
ntsekouras 40192f7
Update src/wp-includes/blocks.php
ntsekouras 3bebb24
Update src/wp-includes/blocks.php
ntsekouras 293533a
Update src/wp-includes/blocks.php
ntsekouras b4769ec
Update src/wp-includes/blocks.php
ntsekouras 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
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.
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.
Technically someone could have a taxonomy named
includeorexclude, no?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.
Technically yes, but I'd consider it very hard to encounter.. This affects the REST API too and people can't use it properly since there is already the
includeto limit the result set to specific IDs and the respective exclude arg.Not sure if we should consider updating
register_taxonomyto have some reserved keys or update the REST API to somehow handle these cases, but maybe it's not worth it since it seems quite edge case to have taxonomies with these names? 🤔