-
Notifications
You must be signed in to change notification settings - Fork 160
Commit e48f452
authored
config/default: Set
- This enumerates all of the currently defined rules that were
implicitly disabled by `DisabledByDefault: true` and make them
explicitly disabled so that there is no functional change to the
RuboCop cops today e.g. if someone upgrades they won't experience a
flood of newly enabled rules.
- This was achieved by briefly re-enabling `DisabledByDefault`, then
running `bundle exec rubocop --show-cops`, and the script included
with the previous commit.
- All of the TODOs from the previous commit about cross-checking newly
enabled rules with the styleguide are gone, since there are no newly
enabled rules, and this should be a better user experience for
downstream consumers since they don't have to scramble to understand
new RuboCop rules that fail in their project (over and above custom
ones they have in their project which will now be enabled because we
removed `DisabledByDefault` in this gem).
- In the future, we'll go through the list of rules here and cross-check
them with the styleguide, potentially migrating some of them to
`Enabled: true`. But this changeset as it is now should be good to ship.Enabled: false
on a bunch of rules1 parent 05e8276 commit e48f452Copy full SHA for e48f452
File tree
Expand file treeCollapse file tree
1 file changed
+738
-816
lines changedFilter options
- config
Expand file treeCollapse file tree
1 file changed
+738
-816
lines changed
0 commit comments