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
Is your feature request related to a problem? Please describe.
#935 added entries to the InverseMethods configuration of Style/InverseMethods. I believe this redundant with existing cops Rails/Present and Rails/NegateInclude, but the Rails cops can be scoped to just the parts of the codebase that enable ActiveSupport (ironically, I became aware of this because it caused errors in the custom RuboCop code used by homebrew.)
Fixesrubocop#888.
This PR makes `Style/InverseMethods` aware of `exists?`.
Probably simpler than implementing a new named cop. And there will be
no overlap with existing cop as reported in rubocop#941.
Is your feature request related to a problem? Please describe.
#935 added entries to the
InverseMethods
configuration ofStyle/InverseMethods
. I believe this redundant with existing copsRails/Present
andRails/NegateInclude
, but theRails
cops can be scoped to just the parts of the codebase that enableActiveSupport
(ironically, I became aware of this because it caused errors in the customRuboCop
code used by homebrew.)Describe the solution you'd like
Revert the
config/default.yml
change in #935Describe alternatives you've considered
Downstream repos could set
InverseMethods
back to the corerubocop
default, but that could lead to drift issues if the core config changes.The text was updated successfully, but these errors were encountered: