Fix NoMethodError when calling selector methods w/o anony config #113
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.
When calling
selector_for?
oranonymise_for!
on a model with noanonymise
block, instead of throwing aNoMethodError
due to the anonymisation config beingnil
we now do the following:false
when callingselector_for?
, same as if callingvalid_anonymisation?
ArgumentError
when callinganonymise_for!
, same as if callinganonymise!