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.

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

can't seem to get API versioning support working #92

Open
enterprise-easyb opened this issue Aug 22, 2018 · 0 comments
Open

can't seem to get API versioning support working #92

enterprise-easyb opened this issue Aug 22, 2018 · 0 comments

Comments

@enterprise-easyb
Copy link

I tried a couple of different approaches including reviewing the source code. Two observations are that it seems like support for API "mostly functional versioning" was added about three years ago based upon a commit message. It then seems like it might have broken about two years ago when the spec parser was switched to go-openapi. There's some reference in the code to an extended x-version property.

What I was expecting was to be able to provide two different yaml files (myspec-1.0.0.yaml and myspec-2.0.0) and that dapperdox would do the right thing. I didn't.

Does anyone know the current state of supporting multiple API versions? Any tips?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant