-
Notifications
You must be signed in to change notification settings - Fork 18
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
Integrate OpenAPI 3 into Dredd #71
Comments
Please see https://github.com/apiaryio/api-elements.js/blob/master/packages/fury-adapter-oas3-parser/STATUS.md for the list of supported features. The support of OpenAPI 3 in Dredd is experimental, beta, early, you name it. It is everything but finished. However, it already works - see apiaryio/api-elements.js#71 The OAS3 adapter is now developed publicly at https://github.com/apiaryio/api-elements.js/tree/master/packages/fury-adapter-oas3-parser and accepts contributions. Close #894
Can I suggest a checklist in the description so we can follow along how far we've got and how long we still have to go? |
A checklist would be helpful to understand better the work done, the work remaining, and the status of the OpenAPI3 support. |
in what state openapiv3 is today? i arrived here from https://blog.apiary.io/OAS-3 , status page does not work https://github.com/apiaryio/api-elements.js/blob/master/packages/fury-adapter-oas3-parser/STATUS.md?rgh-link-date=2018-12-11T00%3A32%3A00Z |
This issue is tracking integrating OpenAPI 3 support into Dredd.
Caveats
The current support is not finished but we want to get OpenAPI 3 to you as quick as we can. We're doing this in the open which allows you to follow the progress, give us early feedback and allows you to contribute desired functionality.
There are some caveats with Dredd support in the current release, most should be addressed next week:
See below for a working example of current functionality.
Important Missing Functionality
See our status page for furher information on supported functionality.
Examples
Success
Failure
The text was updated successfully, but these errors were encountered: