Handling Version Loading in Gems Properly#504
Merged
Conversation
Closed
Closed
Yang-33
deleted the
do-not-require-version-in-gemspec-file-not-to-affect-test
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If the version file is not loaded in the library code but is loaded in the gemspec file, issues like (#379) load errors or missing constants can occur.
To be cautious, the gemspec avoids requiring the version file directly. Instead, it reads the file content. This approach also includes a simple validation to ensure the version string follows the SemVer format, so mistakes in the version file can be detected early.
Additionally, this change fixes an actual case where the version file was not being required properly.