Age | Commit message (Collapse) | Author |
|
Cops with a max level are auto-generated with that set to the current
maximum, even when they're supposed to be ignored. For now, the best
option is to manually disable them.
|
|
|
|
|
|
`Style/VariableNumber` is explicitly disabled because I don't think we
care if we name a variable `var_1` or `var1`.
|
|
|
|
|
|
|
|
Enable Rubocop cops that check access modifiers
## What does this MR do?
This MR enables Rubocop cops that detect methods that should be restricted but are the part of public API because of access modifiers used improperly.
This also fixes existing offenses.
## Why was this MR needed?
Some method in our codebase are public instead of being private because it is sometimes difficult to get it right without static analysis.
## What are the relevant issue numbers?
See #17478
Closes #17372
See merge request !5014
|
|
Avoid multi-line ?: (the ternary operator). Use if/unless instead.
See #17478
|
|
This enables following cops:
Check for useless access modifiers
Lint/UselessAccessModifier
Checks for attempts to use `private` or `protected` to set the
visibility of a class method, which does not work.
Lint/IneffectiveAccessModifier
This also disables two false possitives in concerns.
|
|
|
|
|
|
|
|
|
|
https://github.com/bbatsov/rubocop/blob/v0.41.2/CHANGELOG.md
|