Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for Open API 3.0 #894
Just to reiterate, adding support for a new API description format goes like this...
To produce API Elements for various formats, Fury.js uses adapters. So the first and the most important step to add support for OpenAPI 3.0 to Dredd would be to create an adapter for Fury, similar to the one for Swagger. The Fury.js maintainers (@apiaryio/adt) would definitely give a hand and advice to anyone who starts with this.
Note: A scheme of Dredd's parsing stack is in #820, I'd be happy to re-draw it and add it to docs if there's someone who actually needs it.
referenced this issue
Sep 25, 2018
We, as the team behind the Apiary tools, would like to start with the adapter very soon.
It has two phases. First we need the Fury adapter mentioned earlier, which is the responsibility of @apiaryio/adt. When the adapter is ready, @apiaryio/sjs (currently me) can start working on bringing the very desired OAS3 support to Dredd. The adapter is going to be a parallel repository to https://github.com/apiaryio/fury-adapter-swagger, possibly something like https://github.com/apiaryio/fury-adapter-oas3, so watch out for that and when we kick it off, don't be afraid to give us a hand to make it all faster. See #894 (comment) to understand and do not hesitate to contact us in other issues for help and guidance.
This should stay as a tracking issue of OAS3 support in Dredd. We do track this as the most important thing to be worked on, so there's no need to add more