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
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.
If nothing else is specified in the configuration, use either "1" or the current mix project version as the api version.
Additionally, allow to specify a single global version in the config file.
Additionally, allow to configure BlueBird to use the base path for versioning.
Additionally, allow to configure BlueBird to use the accept header for versioning.
For 3 and 4, generate separate documentation files for each version.
The text was updated successfully, but these errors were encountered:
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"
or the current mix project version as the api version.For 3 and 4, generate separate documentation files for each version.
The text was updated successfully, but these errors were encountered: