-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
pb33f/libopenapi does not support nullable attribute #876
Comments
@h6ah4i Thank you for your report! |
In v0.103.2, nullable attributes for request and response are now supported. Try it out if you like 👍 |
Thank you for the rapid response! However, the workaround introduced in v0.103.2 did not helped me in my setup unfortunately. It seems the current workaround only support very basic syntax of OpenAPI, so it did not work for schema files using [ Could you take a look at the following code that I have added some test cases into the |
In v0.103.3, I fixed it to pass the test you added. Thank you! |
@k1LoW Thank you so much! It seems like the validation failure caused by the Still, I get many OpenAPI validation errors in v0.100.0+, so I have reported two new issues. |
Thank you!! |
Hi. I noticed an issue that blocks me to use runn v0.100 or newer. Recent versions of runn use pb33f/libopenapi-validator for validating API requests and responses. The library has an issue that does not support
nullable
property. Unfortunately, the author of libopenapi gave up to support them due to relying its validation feature is depends on third-party library...ref.) pb33f/libopenapi#265 nullable: true for response validation
The text was updated successfully, but these errors were encountered: