We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Mojo param parsing behaves as if allowEmptyValue is true, which is not the openapi default:
for my $pair (split /&/, $str) { next unless $pair =~ /^([^=]+)(?:=(.*))?$/; my ($name, $value) = ($1, $2 // ''); ...
If we want to verify that empty values aren't passed, then we need to parse the parameters ourselves and error when $2 is undef.
The text was updated successfully, but these errors were encountered:
Just as in #63, this is difficult to do without having access to the original request (Mojo::Parameters::pairs turns a missing query value into '').
Sorry, something went wrong.
allowEmptyValue recently saw some clarification in the spec: OAI/OpenAPI-Specification#3835
allowEmptyValue
..which is reflected here via commit 061d164, which was released in v0.065.
No branches or pull requests
Mojo param parsing behaves as if allowEmptyValue is true, which is not the openapi default:
If we want to verify that empty values aren't passed, then we need to parse the parameters ourselves and error when $2 is undef.
The text was updated successfully, but these errors were encountered: