feat: client query negation #3805
Open
Conversation
This file contains 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
|
|
awill1988
force-pushed
the
feat-client-query-negation
branch
from
500a2e0
to
b45486c
Compare
awill1988
force-pushed
the
feat-client-query-negation
branch
3 times, most recently
from
f7f8fcd
to
18295d4
Compare
awill1988
force-pushed
the
feat-client-query-negation
branch
from
18295d4
to
aca1c66
Compare
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.
👋🏻 I am new here so I apologize in advance for what is likely a contribution that needs work so I am happy to take plenty of feedback and work towards whatever solution makes the most sense.
The goal of this is to add a concise (and safe) way to specify some negative matching criteria on the HTTP API by expanding the way the query parameters are interpreted when requesting a list of OAuth2 Clients.
Related issue(s)
#3804
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments
Before I forget to mention it, thank you for this wonderful software!