New issue
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
With YAML::Syck, additionalProperties: false
is treated as true
#27
Labels
Comments
Thanks for the excellent test case! 👍 Going to make a new release on CPAN in a couple of hours. |
jhthorsen
pushed a commit
that referenced
this issue
Aug 16, 2016
jhthorsen
pushed a commit
that referenced
this issue
Aug 16, 2016
- Fix handling of true/false in schema, when loaded with YAML::Syck #27 - Add EXPERIMENTAL support for passing $json_path to validate()
jhthorsen
pushed a commit
that referenced
this issue
Oct 23, 2018
jhthorsen
pushed a commit
that referenced
this issue
Oct 23, 2018
- Add support for using operationId instead of x-mojo-controller #36 #37 - Add "swagger_route_added" event #27 - Remove "valid" from standard error structure since it was redundant - Documented how to include http://git.io/vcKD4
elcamlost
pushed a commit
to elcamlost/json-validator
that referenced
this issue
Aug 30, 2019
elcamlost
pushed a commit
to elcamlost/json-validator
that referenced
this issue
Aug 30, 2019
elcamlost
pushed a commit
to elcamlost/json-validator
that referenced
this issue
Aug 30, 2019
- Fix handling of true/false in schema, when loaded with YAML::Syck jhthorsen#27 - Add EXPERIMENTAL support for passing $json_path to validate()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using YAML::Syck, the validator does not complain about
additional properties, despite
additionalProperties: false
schema.yaml:
https://github.com/jhthorsen/json-validator/blob/master/lib/JSON/Validator.pm#L548
here
$additional
has the valuefalse
as a string.The text was updated successfully, but these errors were encountered: