Add support for Open API 3.0

[johngluckmdsol]

It appears that version 3.0 is not yet supported. We're hoping to move to Open API 3.0 because we are better able to represent our JSON Schema with it. It would be great if your tool could suppor it.

[honzajavorek]

Regarding the Open API 3.0, we plan to support it, the question is when and the answer is yet to be determined. Of course anyone can come and contribute the support at any time, and we'll be there to help them - see #837 (comment)

Related issues: apiaryio/fury-adapter-swagger#131

[JurRutten]

+1

[veewee]

+1

[XVincentX]

Same here. I'd love to put the express-gateway API under tests but our specs are written in Open API 3.0!

[tombevers]

+1

[jonas-depop]

+1

[honzajavorek]

@tombevers @jonas-depop @JurRutten @veewee We understand this is a wanted feature, but next time please use GitHub Reactions to express your feelings. Thanks! ✨

By the way, one of the benefits is we can sort by the reactions:

[honzajavorek]

Just to reiterate, adding support for a new API description format goes like this...

Dredd consumes API Elements. It uses Fury.js to turn any API description format (currently API Blueprint and Swagger 2.0) into API Elements.

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.

[altcatalin]

+1

[YGeorge]

Any update on this?

[michalholasek]

@YGeorge Implementation for initial OAS3 support is scheduled to start soon, but we don't have more accurate timeframe yet.

[joost]

+1

[nesl247]

@michalholasek Is there a timeframe at this point? It's been a few months since the last update. Curious to see how it's going.