Grape::API versioning based on request parameter. #175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added an API versioner which searches for a named parameter (default is 'apiver') to find the specified api version. The name of the parameter can be changed via the 'parameter' option when specifying the version. Include all the same specs as already existed for the other versioners. Update README markdown to explain this new versioning strategy.
|
Implemented this for internal use and cleaned it up in case you wanted to merge it upstream. Thank you for Grape! |
|
This has been open for a while and nobody seems to be unhappy with it. Thank you, merging. |
dblock
added a commit
that referenced
this pull request
Jun 4, 2012
Grape::API versioning based on request parameter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an API versioner which searches for a named parameter (default is
'apiver') to find the specified api version. The name of the parameter
can be changed via the 'parameter' option when specifying the version.
Include all the same specs as already existed for the other versioners.
Update README markdown to explain this new versioning strategy.