Make RuboCop aware of Rails concerning
and delegate
methods
#21
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.
In its default configuration, RuboCop's
Lint/UselessAccessModifier
rule can get confused by theconcerning
anddelegate
constructs in Rails.Take this code for example,
RuboCop sees two
private
modifiers and considers this a violation, even though they take place in two different scopes.This PR fixes this by configuring
Lint/UselessAccessModifier
to understand Rails-specific syntax, as recommended in the RuboCop docs: https://docs.rubocop.org/rubocop/cops_lint.html#lintuselessaccessmodifier