-
Notifications
You must be signed in to change notification settings - Fork 471
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
Add version handling #152
Add version handling #152
Conversation
- Repurposing api_version to pull desired version from query string. - Only routes for the specified version will be returned.
Making Swagger respect versions
This needs tests and a rebase to be merged, please. |
+1 |
Bump. |
@dblock What's blocking this from a merge? Tests? |
Yes, tests + rebase. |
Does it work? |
Hello, what's the status on this ? |
There's code, no tests. Please finish this PR. |
We are still looking into this, there is a javascript issue that have to be resolved for these changes to work. @MathieuGilbert @mvandenbeuken |
Bump for this, it's been a while with no update. 👊 |
please re-target against |
@rubene this is something that'd be great to have. was it ever picked up again in another pull request? |
what was the javascript issue? |
@MathieuGilbert @mvandenbeuken @rubene I would also like to know wha the issues were, and if this will ever be merged. |
Give ability to grape-swagger to distinguish and handle multiple grape api versions.
Repurposing api_version to pull desired version from query string.
Only routes for the specified version will be returned
Possible related issues:
141
146
38