doc(#2380): Updating versioning section inside the README #2381
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
jcagarcia
force-pushed
the
issue-2380
branch
from
e208ef6 to
afdeb66
Compare
dblock
approved these changes
Nov 28, 2023
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.
Hi 👋 I made a suggestion about how to version in (what I thought it was) an easy way. However, this is totally solved and really well explained in https://code.dblock.org/2013/07/19/evolving-apis-using-grape-api-versioning.html
So I think my problem was that I was not able to find in the documentation that multiple versions for the same
Grape::APIclass were allowed and a little guide about how to properly use versioning.Do you think this can help?