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

Add support for Open API 3.0 #894

Open
johngluckmdsol opened this Issue Oct 13, 2017 · 19 comments

Comments

Projects
None yet
@johngluckmdsol

johngluckmdsol commented Oct 13, 2017

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

This comment has been minimized.

Show comment
Hide comment
@honzajavorek

honzajavorek Oct 17, 2017

Member

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

Member

honzajavorek commented Oct 17, 2017

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

This comment has been minimized.

Show comment
Hide comment
@JurRutten

JurRutten commented Oct 30, 2017

+1

@veewee

This comment has been minimized.

Show comment
Hide comment
@veewee

veewee commented Oct 30, 2017

+1

@XVincentX

This comment has been minimized.

Show comment
Hide comment
@XVincentX

XVincentX Oct 30, 2017

Contributor

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

Contributor

XVincentX commented Oct 30, 2017

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

@tombevers

This comment has been minimized.

Show comment
Hide comment
@tombevers

tombevers commented Oct 31, 2017

+1

@jonas-depop

This comment has been minimized.

Show comment
Hide comment
@jonas-depop

jonas-depop commented Nov 24, 2017

+1

@honzajavorek

This comment has been minimized.

Show comment
Hide comment
@honzajavorek

honzajavorek Nov 30, 2017

Member

@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:

image

Member

honzajavorek commented Nov 30, 2017

@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:

image

@honzajavorek

This comment has been minimized.

Show comment
Hide comment
@honzajavorek

honzajavorek Jan 3, 2018

Member

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.

Member

honzajavorek commented Jan 3, 2018

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.

@honzajavorek honzajavorek referenced this issue Jan 18, 2018

Closed

Fix reference to the OpenAPI Specification #950

1 of 3 tasks complete
@altcatalin

This comment has been minimized.

Show comment
Hide comment
@altcatalin

altcatalin commented Jan 18, 2018

+1

@YGeorge

This comment has been minimized.

Show comment
Hide comment
@YGeorge

YGeorge Mar 30, 2018

Any update on this?

YGeorge commented Mar 30, 2018

Any update on this?

@michalholasek

This comment has been minimized.

Show comment
Hide comment
@michalholasek

michalholasek Apr 5, 2018

Contributor

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

Contributor

michalholasek commented Apr 5, 2018

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

@joost

This comment has been minimized.

Show comment
Hide comment
@joost

joost Apr 26, 2018

Contributor

+1

Contributor

joost commented Apr 26, 2018

+1

@nesl247

This comment has been minimized.

Show comment
Hide comment
@nesl247

nesl247 Jul 30, 2018

@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.

nesl247 commented Jul 30, 2018

@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.

@michalholasek

This comment has been minimized.

Show comment
Hide comment
@michalholasek

michalholasek Jul 31, 2018

Contributor

@nesl247 There's no update on the timeframe yet, unfortunately.

Contributor

michalholasek commented Jul 31, 2018

@nesl247 There's no update on the timeframe yet, unfortunately.

@Miouge1

This comment has been minimized.

Show comment
Hide comment
@Miouge1

Miouge1 Aug 21, 2018

Is there any alternatives to dredd to test OpenAPI 3.0?

Miouge1 commented Aug 21, 2018

Is there any alternatives to dredd to test OpenAPI 3.0?

@orontee

This comment has been minimized.

Show comment
Hide comment
@orontee

orontee commented Aug 30, 2018

+1

@jurgob

This comment has been minimized.

Show comment
Hide comment
@jurgob

jurgob commented Sep 8, 2018

+1

@jcagarcia

This comment has been minimized.

Show comment
Hide comment
@jcagarcia

jcagarcia commented Sep 26, 2018

+1

@honzajavorek

This comment has been minimized.

Show comment
Hide comment
@honzajavorek

honzajavorek Sep 26, 2018

Member

@joost @jcagarcia @jurgob @orontee I'm sorry, but this is not helpful. See #894 (comment) I'm going to lock this issue now.

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 👍 . We hear you.

Thanks!

Member

honzajavorek commented Sep 26, 2018

@joost @jcagarcia @jurgob @orontee I'm sorry, but this is not helpful. See #894 (comment) I'm going to lock this issue now.

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 👍 . We hear you.

Thanks!

@apiaryio apiaryio locked and limited conversation to collaborators Sep 26, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.