Command determines ARGV correctly when ARGV empty #59
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.
Usually if you call
rake appraisal
from a project configured to use Appraisal, then everything works -- Appraisal callsrake
for each of your gemfiles.However, if you've configured
rake
to runrake appraisal
automatically, when you callrake
then Appraisal::Command throws an error. This is because it assumes that "appraisal" will be first in ARGV, which is the case when you callrake appraisal
manually but not the case here. Therefore when it tries to figure out which command to run it blows up (as ARGV[1..-1] returns nil if ARGV is empty). This commit fixes that.NOTE: I'm not sure how to test this? Is there a way?