-
Notifications
You must be signed in to change notification settings - Fork 43
Validation error on nullable parameters with a format #34
Comments
Welcome and thank you for the report. Can you confirm the fix in the latest snapshot? It should be already available. |
@llfbandit Thank you for the quick response. Also, is there an estimate on when 0.6 will be released? |
You have to add I'm waiting for #28 confirmation before bumping to 0.7 so a couple of days I would say. |
The above test throws a |
This is due to the usage of If you really use the toolset like with the reproducer you'll need to use To let me know, what kind of usage do you have? For this kind of validation process, the operation validator is dedicated to make the glue code between parser and schema validation modules. |
I updated the code to |
We are using the schema validator to validate input and output payloads against the schemas defined in the OpenAPI definition of the REST API. |
0.6 introduced this bug. Sorry for that. |
Can you validate this issue ? We're pretty close to conclude on the other side. Thank you. |
Validated. Seems to be fixed. Thank you very much for the quick turnaround. |
Describe the bug
A validation error is issued by
SchemaValidator
when a nullable number property with a format (e.g.double
) isnull.
To Reproduce
The following error is displayed when the above code is run:
Expected behavior
Expected no validation errors from the above code.
The text was updated successfully, but these errors were encountered: