Fix empty query parameter schema validation - #1224
Open
rootsec1 wants to merge 1 commit into
Open
Conversation
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
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.
An empty query value is rejected before schema validation whenever
allowEmptyValueis omitted. This prevents schemas that explicitly allow an empty string, including enum values, from taking effect.The empty-value error is now raised only when
allowEmptyValueis explicitly false. When the deprecated field is absent, the schema decides whether the empty string is valid; explicit false behavior and warnings remain unchanged.Tests cover validation and unmarshalling across OpenAPI 3.0, 3.1, and 3.2, including schema-allowed and rejected empty strings, explicit false, and omitted optional parameters.
Closes #1210