diff options
| author | Daniel Colson <danieljamescolson@gmail.com> | 2018-04-17 08:37:35 -0400 |
|---|---|---|
| committer | Daniel Colson <danieljamescolson@gmail.com> | 2018-04-19 08:11:28 -0400 |
| commit | 087e0ccb72e7a1491701dd1d1d49746f745d9d68 (patch) | |
| tree | da79375760e74db0bc466695cce13689666ef430 /activesupport/test/key_generator_test.rb | |
| parent | ef2af628a9ec1cc4e7b6997a021dd3f85cfe4665 (diff) | |
| download | rails-087e0ccb72e7a1491701dd1d1d49746f745d9d68.tar.gz rails-087e0ccb72e7a1491701dd1d1d49746f745d9d68.tar.bz2 rails-087e0ccb72e7a1491701dd1d1d49746f745d9d68.zip | |
Add RuboCop for `assert_not` over `assert !`
We added `assert_not` in f75addd "to replace warty 'assert !foo'".
fa8d35b 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?
Diffstat (limited to 'activesupport/test/key_generator_test.rb')
0 files changed, 0 insertions, 0 deletions