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

Transition/Support for OpenAPI 3.0.0 Specification #514

Open
edgeadjei opened this Issue Jul 26, 2017 · 11 comments

Comments

Projects
None yet
10 participants
@edgeadjei

edgeadjei commented Jul 26, 2017

Can we expect support for the OpenAPI 3.0.0 specification?
OpenAPI-Specification

@kapildave6

This comment has been minimized.

Show comment
Hide comment
@kapildave6

kapildave6 Sep 14, 2017

Any update on this? Can we expect support for 3.0.0 in swagger-node?

kapildave6 commented Sep 14, 2017

Any update on this? Can we expect support for 3.0.0 in swagger-node?

@sakes

This comment has been minimized.

Show comment
Hide comment
@sakes

sakes Sep 15, 2017

@fehguy @theganyo Can we get an official response to the original question? I'm assuming this tool will be reworked once the swagger-api contributors are satisfied with the migration of other core swagger-api libs to 3.0?

Do you guys need some help with swagger-node?

sakes commented Sep 15, 2017

@fehguy @theganyo Can we get an official response to the original question? I'm assuming this tool will be reworked once the swagger-api contributors are satisfied with the migration of other core swagger-api libs to 3.0?

Do you guys need some help with swagger-node?

@kapildave6

This comment has been minimized.

Show comment
Hide comment
@kapildave6

kapildave6 Sep 26, 2017

@fehguy @theganyo @sakes

Any update?
Can we have expected date for release?

kapildave6 commented Sep 26, 2017

@fehguy @theganyo @sakes

Any update?
Can we have expected date for release?

@webron

This comment has been minimized.

Show comment
Hide comment
@webron

webron Sep 29, 2017

Member

Hi everyone - sorry for the delayed reply.

It is our intent to support OAS3 in swagger-node. This is not going to be an easy transition as a lot of things are going to change under the hood of the project. We cannot provide you with an ETA, but I can say that we'll only be able to start working on it after we finish full OAS3 support in our other Javascript projects (swagger-js/ui/editor).

Member

webron commented Sep 29, 2017

Hi everyone - sorry for the delayed reply.

It is our intent to support OAS3 in swagger-node. This is not going to be an easy transition as a lot of things are going to change under the hood of the project. We cannot provide you with an ETA, but I can say that we'll only be able to start working on it after we finish full OAS3 support in our other Javascript projects (swagger-js/ui/editor).

This was referenced Sep 29, 2017

@drej1

This comment has been minimized.

Show comment
Hide comment
@drej1

drej1 Oct 26, 2017

Hi @webron ! So how is it going with the other js projects? Still work in progress?
Do you have a high level roadmap for this project?
Thank You very much.
Drej

drej1 commented Oct 26, 2017

Hi @webron ! So how is it going with the other js projects? Still work in progress?
Do you have a high level roadmap for this project?
Thank You very much.
Drej

@webron

This comment has been minimized.

Show comment
Hide comment
@webron

webron Oct 26, 2017

Member

That's a very fair question. The other JS projects are progressing fairly well, but we still have some time to invest in them. Wish I could give you an ETA but anything I would give you would be pretty much random. I would not expect to see a version before the end of the year.

Member

webron commented Oct 26, 2017

That's a very fair question. The other JS projects are progressing fairly well, but we still have some time to invest in them. Wish I could give you an ETA but anything I would give you would be pretty much random. I would not expect to see a version before the end of the year.

@phamdt

This comment has been minimized.

Show comment
Hide comment
@phamdt

phamdt Dec 15, 2017

are there any tasks that could be given to the community to take on to help with the transition?

phamdt commented Dec 15, 2017

are there any tasks that could be given to the community to take on to help with the transition?

@scottmdahl

This comment has been minimized.

Show comment
Hide comment
@scottmdahl

scottmdahl Feb 5, 2018

@webron Any updates on this issue? Anything the community can do to help?

scottmdahl commented Feb 5, 2018

@webron Any updates on this issue? Anything the community can do to help?

@jwalton

This comment has been minimized.

Show comment
Hide comment
@jwalton

jwalton May 22, 2018

I've spent the past several weeks writing a new OpenAPI 3.x.x framework for node.js from the ground up. You can check it out here.

jwalton commented May 22, 2018

I've spent the past several weeks writing a new OpenAPI 3.x.x framework for node.js from the ground up. You can check it out here.

@ewoudsmets

This comment has been minimized.

Show comment
Hide comment
@ewoudsmets

ewoudsmets May 25, 2018

@jwalton Exegesis is looking fairly similar as swagger-node but I prefer to stick to the existing framework. Still hope OpenAPI3 will soon be supported by swagger-node.
Does anybody know if there will be a migration path from OpenAPI2 -> OpenAPI3 supported by swagger-node?

ewoudsmets commented May 25, 2018

@jwalton Exegesis is looking fairly similar as swagger-node but I prefer to stick to the existing framework. Still hope OpenAPI3 will soon be supported by swagger-node.
Does anybody know if there will be a migration path from OpenAPI2 -> OpenAPI3 supported by swagger-node?

@sumitgoelpw

This comment has been minimized.

Show comment
Hide comment
@sumitgoelpw

sumitgoelpw Jun 7, 2018

@webron do you have any update for us about OpenAPI 3.0 support?

sumitgoelpw commented Jun 7, 2018

@webron do you have any update for us about OpenAPI 3.0 support?

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