You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: the remaining offense:
>Line #14 – Convention: Rails/LexicallyScopedActionFilter: list_sequences, show_sequence, next_sequence, prev_sequence are not explicitly defined on the class.
appears to be due to a bug, which I have reported. rubocop/rubocop-rails#263
When a method is aliased in the class, using that method in a filter should not trigger a LexicallyScopedActionFilter offense.
Note: I submitted this as a Bug Report, but perhaps it should instead be a Feature Request.
Expected behavior
Using aliased methods in a filter causes LexicallyScopedActionFilter offenses.
Actual behavior
Using aliased methods in a filter should not cause LexicallyScopedActionFilter offenses.
Steps to reproduce the problem
Run RuboCop on the following:
RuboCop version
The text was updated successfully, but these errors were encountered: