Rake::TaskArguments#key? alias of #has_key? #175
Merged
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.
This PR adds
Rake::TaskArguments#key?(key)
as an alias ofhas_key?(key)
.Rake::TaskArguments
exposes a Hash-like interface including#has_key?(key)
, but is missing#key?(key)
. Making this worse, themethod_missing
behaviour meansargs.key?(:foo)
does not raise NoMethodError, instead treating it likeargs[:key?]
and generally returningnil
.The commonly referenced ruby-style-guide says:
which links to matz saying:
RuboCop's
Style/PreferredHashMethods
rule complains about usinghas_key?
:However accepting its solution of using
#key?
causes silent failure viamethod_missing
as described above.