Add RuboCop for `assert_not` over `assert !`
We added `assert_not` in f75addd0 "to replace warty 'assert !foo'". fa8d35b4 agrees that it is warty, and so do I. This custom Rubocop rule turns the wart into a violation. As with my last custom cop, https://github.com/rails/rails/pull/32441, I want to make sure this looks right on code climate before pushing another commit to autocorrect everything. @toshimaru I just noticed https://github.com/toshimaru/rubocop-rails/pull/26 Is there a better way to add these custom cops, or were you saying we shouldn't have custom cops at all?
Showing
想要评论请 注册 或 登录