Skip to content
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

Closed
kibertoad opened this issue Jul 11, 2018 · 5 comments
Closed

OpenAPI 3.0 support #34

kibertoad opened this issue Jul 11, 2018 · 5 comments

Comments

@kibertoad
Copy link
Collaborator

kibertoad commented Jul 11, 2018

An approach to investigating missing swagger features is a good question.
Suggested reading:

  1. Supported data types
  2. Validation for parameters
  3. Security Defenitions

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.

@idanto
Copy link
Contributor

idanto commented Feb 22, 2019

So now that we have support in openAPI 3.0, would you like to do some of those tests? @kibertoad

@kibertoad
Copy link
Collaborator Author

Sure!

@idanto
Copy link
Contributor

idanto commented Apr 15, 2019

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 ?

@kibertoad
Copy link
Collaborator Author

@idanto Makes sense!

@kibertoad
Copy link
Collaborator Author

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
Labels
None yet
Development

No branches or pull requests

2 participants