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

Support api versioning #13

Open
woylie opened this issue Jun 22, 2017 · 0 comments
Open

Support api versioning #13

woylie opened this issue Jun 22, 2017 · 0 comments

Comments

@woylie
Copy link
Member

woylie commented Jun 22, 2017

Right now, BlueBird doesn't support api versioning. Everything is put into one single documentation. However, a version must be specified in Swagger. I suggest to gradually add support for api versioning.

  1. If nothing else is specified in the configuration, use either "1" or the current mix project version as the api version.
  2. Additionally, allow to specify a single global version in the config file.
  3. Additionally, allow to configure BlueBird to use the base path for versioning.
  4. Additionally, allow to configure BlueBird to use the accept header for versioning.

For 3 and 4, generate separate documentation files for each version.

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

No branches or pull requests

1 participant