Changes to support swagger 1.2 #1661
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
we just can't support the older version now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've started maintaining a project for which the upgrade from Swagger 1.2 to 2 is unlikely to happen in the near future, it's going to involve quite a lot of work and due to OAI/OpenAPI-Specification#182 it's unlikely we'll even be able to upgrade.
I've been maintaining achingbrain/swagger-ui-browserify to address #1596 - this PR contains the changes necessary to support the older swagger-ui and as such the older Swagger spec.
You probably won't be able to merge this PR directly but perhaps you could create a branch from the 2.0.24 tag, merge these changes in and release it as 2.0.25?