You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2019. It is now read-only.
Since there is the goal of adding v1 v2 v3 support, instead of versioning out each Swagger instance, it's possible to refactor the existing swagger cli tool and identify the Swagger Version from the yaml/json file in order to determine which parser to use?
Additional Information
Essentially it would change the cli to only have a single swagger command, and the json/yaml file would dictate which parser to use inside of the service.
Issue Checklist
Maintainer has viewed
Loaded into Backlog
PR submitted [Link Here](Eventual Link)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Refactor Swagger CLI
Details
Since there is the goal of adding v1 v2 v3 support, instead of versioning out each Swagger instance, it's possible to refactor the existing swagger cli tool and identify the Swagger Version from the yaml/json file in order to determine which parser to use?
Additional Information
Essentially it would change the cli to only have a single swagger command, and the json/yaml file would dictate which parser to use inside of the service.
Issue Checklist
The text was updated successfully, but these errors were encountered: