This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Properly register "{taxonomy}_exclude" parameters in the schema#2802
Merged
Properly register "{taxonomy}_exclude" parameters in the schema#2802
Conversation
PR #2756 added an `_exclude` complement to every registered taxonomy query parameter method, e.g. `categories_exclude`, to permit an API consumer to list an array of term IDs with which returned posts should NOT be associated. However, that PR omitted the important step of registering the parameters on the schema! This PR does so.
joehoyle
approved these changes
Oct 12, 2016
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 #2756 added an
_excludecomplement to every registered taxonomy query parameter method, e.g.categories_exclude, to permit an API consumer to list an array of term IDs with which returned posts should NOT be associated. However, that PR omitted the important step of registering the parameters on the schema! This PR does so.