-
Notifications
You must be signed in to change notification settings - Fork 50
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
OpenAPI 3.0 support #34
Comments
So now that we have support in openAPI 3.0, would you like to do some of those tests? @kibertoad |
Sure! |
I think we can move this list to api-schema-builder cause we get the support from the extracted package, or at least duplicate it there cause we probably would like to have few tests here. wdyt @kibertoad ? |
@idanto Makes sense! |
Moved to PayU/api-schema-builder#23 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An approach to investigating missing swagger features is a good question.
Suggested reading:
Those are probably the core features that related to input validation.
The approach in my opinion should be to start writing tests for each of the keywords and see the behavior, In case it is not as expected we can open an issue and fix it.
We also know that we miss support in multiple swagger file but that's a known issue that we shouldn't address now.
The text was updated successfully, but these errors were encountered: