276 - Update .ruby-version file to 3.2.2 #277
Merged
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
hortongn
approved these changes
Nov 21, 2023
hortongn
deleted the
update-276-make-ruby-version-file-compatible-rvm-rbenv
branch
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.
Fixes #276
The change in the .ruby-version file from
ruby-3.2.2to3.2.2, is actually a minor but important detail. This file is used by version management tools like rbenv or RVM to automatically set the Ruby version for the project.With the ruby- Prefix: When the version is specified with the ruby- prefix (like ruby-3.2.2), it's typically a convention followed by RVM. RVM understands this prefix and sets the appropriate Ruby version for the project.
Without the ruby- Prefix: On the other hand, when the version is specified without the prefix (just 3.2.2), it's more universally recognized, especially by rbenv. Rbenv prefers the version number without any prefix.
The decision to change this file should be based on the version manager your project and team are using. If there's a mix or if you're using rbenv, keeping the version number without the prefix (3.2.2) would be more inclusive and less error-prone.