Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade Swagger 2.0 to Open API Specification 3.0 #2146

Closed
nazarhussain opened this issue Jun 20, 2018 · 3 comments
Closed

Upgrade Swagger 2.0 to Open API Specification 3.0 #2146

nazarhussain opened this issue Jun 20, 2018 · 3 comments
Labels
status: wontfix

Comments

@nazarhussain
Copy link
Contributor

Expected behavior

The latest version of swagger is renamed to OAS3. It have plenty of improvements that we can utilized. Specially the multi server definition.

Actual behavior

We are using Swagger 2.0 currently. Which is kind of near to obsolete.

Steps to Develop

  1. We are using swagger-node-runner which does not support OAS3
  2. Either we fork and upgrade swagger-node-runner to support OAS3
  3. Or instead the package sway package directory, which is the dependency of swagger-node-runner right now.
  4. Upgrade the swagger specification we currently have in swagger.yml
  5. Update the functional tests (if any change made in endpoints)

Which version(s) does this affect? (Environment, OS, etc...)

1.0.0
@nazarhussain nazarhussain added this to the Version 1.1.0 milestone Jun 20, 2018
@nazarhussain nazarhussain self-assigned this Jun 20, 2018
@nazarhussain
Copy link
Contributor Author

nazarhussain commented Jun 28, 2018 •
edited

@MaciejBaj An underlaying core library still don't support OAS3. So we should wait a bit further to see if its updated, then we will port our APIs.

apigee-127/sway#128 (comment)

@nazarhussain nazarhussain mentioned this issue Jun 29, 2018
Closed
@MaciejBaj MaciejBaj modified the milestones: Version 1.1.0, Version 1.2.0 Jul 4, 2018
@nazarhussain
Copy link
Contributor Author

Un-assigning from myself. We will revisit this issue in coming releases and then assign available resource.

@nazarhussain nazarhussain removed their assignment Jul 5, 2018
@diego-G diego-G removed this from the Version 1.2.0 milestone Jul 27, 2018
@shuse2
Copy link
Member

shuse2 commented May 13, 2020

Closing this in favor of #5213 , we will not use swagger runner , but the swagger.yaml will be used for documentation purpose.

@shuse2 shuse2 closed this as completed May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nazarhussain @diego-G @shuse2 @MaciejBaj @sridharmeganathan