97e826f2a4
This method is ambiguous. Sometimes we use it to set invalid data in tests (which can usually be done with `update_column`), and other times we use it instead of `update!`. I'm removing it because, even if sometimes it could make sense to use it, it's too similar to `update_attributes` (which is an alias for `update` and runs validations), making it confusing. However, there's one case where we're still using it: in the ActsAsParanoidAliases module, we need to invoke the callbacks, which `update_column` skips, but tests related to translations fail if we use `update!`. The reason for this is the tests check what happens if we restore a record without restoring its translations. But that will make the record invalid, since there's a validation rule checking it has at least one translation. I'm not blacklisting any other method which skips validations because we know they skip validations and use them anyway (hopefully with care).
29 lines
404 B
YAML
29 lines
404 B
YAML
inherit_from: .rubocop_basic.yml
|
|
|
|
Performance/CompareWithBlock:
|
|
Enabled: true
|
|
|
|
Performance/Detect:
|
|
Enabled: true
|
|
|
|
Performance/DoubleStartEndWith:
|
|
Enabled: true
|
|
|
|
Performance/EndWith:
|
|
Enabled: true
|
|
|
|
Performance/StartWith:
|
|
Enabled: true
|
|
|
|
Rails/HasManyOrHasOneDependent:
|
|
Enabled: true
|
|
|
|
Security/JSONLoad:
|
|
Enabled: true
|
|
|
|
Security/MarshalLoad:
|
|
Enabled: true
|
|
|
|
Security/YAMLLoad:
|
|
Enabled: true
|