Fix parameter types for GET operations#924
Merged
Conversation
|
Formatting check succeeded! |
JPercival
approved these changes
Feb 19, 2026
Contributor
JPercival
left a comment
JPercival
left a comment
There was a problem hiding this comment.
issue: we should have explicit get versus put test so that this asymmetry in the behavior is documented in code
barhodes
force-pushed
the
fix-operation-provider-get-params
branch
from
5623b7d to
f36f74a
Compare
|
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
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.
If an operation is expected to be used as a GET then the parameters must be primitive. This disallows the use of the generic ParametersParameterComponent for any parameters expected to be passed in the query string.