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
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: