Fix __FILE__ and __dir__ in primary Gemfiles
#193
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
nickcharlton
approved these changes
Feb 3, 2022
Open
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.
Appraisal is good! I found a bug: I have the habit of using
ruby Pathname.new(__dir__).join(".ruby-version").readin myGemfile, so that I can write my ruby version in just one place, in the.ruby-versionfile.Unfortunately, the Gemfile classes calls
instance_evalwithout telling Ruby what file the string came from, and so Ruby thinks that FILE should point to appraisal/lib/appraisal/gemfile.rb instead of the Gemfile itself, and that breaks anything inside the Gemfile that references either__FILE__or__dir__.This PR adds a test and passes in the path to the Gemfile, if it is known, to fix that.