Swagger support #1236
Draft
Swagger support #1236
Conversation
This file contains 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
…er 2.x and OpenAPI 3.0.x specs
…tents instead of OpenAPIParser.readLocation
- Added a minor fix to how path params are handled - Added a basic test for Swagger 2.0
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.
What:
Support for Swagger 2.0 specs
Why:
To reduce work for users who have to convert Swagger 2.0 spec to OpenAPI 3.0.x before it can be used with Specmatic
How:
Swagger parser allows internal conversion of Swagger 2.0 to OpenAPI 3.0.x at the time of reading the spec.
Checklist: