Read spec version from swagger spec via codegen tools #23
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
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.
The idea of this PR is to ensure that version extraction from swagger specs supports YAML format too.
In order to avoid adding a new dependency (
org.yaml.snakeyaml) and manually reading the file I've opted to delegate the parsing process toSwaggerParserprovided by swagger-codegen.NOTE: The check in
readVersionFromSpecfileis not needed in case the specs are valid as#/info/versionis required. As we don't revalidate the specs adding the check gives us the flexibility of supporting slightly invalid specs as well