fix: add guard clause to check if matches is nil #917
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.
Hi,
After the release of Country version 8, certain parts of our application began breaking with the following error:
We traced the issue to the
matches
variable beingnil
and still being accessed with an index infinder_methods
. To reproduce this, I’ve added a spec that demonstrates the failure.This PR fixes the issue by adding a guard clause to return early, if
matches
isnil
preventing theNoMethodError
.Our Usage
The behavior surfaced when using the gem in combination with the CanCanCan authorization gem. Internally, CanCanCan calls
respond_to?(:arr)
on theISO3166::Country
object. That call triggered the error shown above.If this fix isn’t appropriate or there's a preferred way of doing it, kindly comment :)