-
Notifications
You must be signed in to change notification settings - Fork 160
config/default: Stop disabling all cops by default #117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
f874c43
config/default: Stop disabling all cops by default
issyl0 87eaa0c
config/default: Remove redundant `Enabled: true` for cops
issyl0 638d418
Autocorrect RuboCop `Layout/EmptyLines` offenses
issyl0 0ca6227
Autocorrect RuboCop `Layout/SpaceInsideHashLiteralBraces` offenses
issyl0 f107008
Autocorrect RuboCop `Style/StringConcatenation` offenses
issyl0 d7ddb57
Autocorrect RuboCop `Style/IfUnlessModifier` offenses
issyl0 cc0a4b8
config/default: Disable some of the default rules
issyl0 8d8c578
Configure and autocorrect RuboCop `Style/PercentLiteralDelimiters`
issyl0 5241eb0
Autocorrect RuboCop `Style/RedundantParentheses` offenses
issyl0 89ac526
config/default: Disable more rules
issyl0 51aa7fb
Autocorrect RuboCop \`Style/SafeNavigation\` offenses
issyl0 401c927
Autocorrect RuboCop `Layout/SpaceAroundOperators` offenses
issyl0 5ba9ba8
config/default: Disable more rules that the styleguide doesn't opine on
issyl0 127c051
Autocorrect RuboCop `Layout/EmptyLineAfterGuardClause` offenses
issyl0 30fe0a5
Autocorrect RuboCop `Layout/RedundantLineBreak` offenses
issyl0 be167bb
Fix RuboCop `Naming/MemoizedInstanceVariableName` offenses
issyl0 9b62169
Autocorrect RuboCop `Style/MultipleComparison` offenses
issyl0 2672610
Autocorrect RuboCop `Style/{RedundantFreeze,MutableConstants}` offenses
issyl0 a53163c
Fix RuboCop `Lint/UselessAssignment` offenses
issyl0 1557c29
config/default: Disable `Lint/AssignmentInCondition` with a big TODO
issyl0 816ca3a
Merge branch 'master' into rubocop-enabled-by-default
issyl0 e2b3734
config/default: Unset `EnabledByDefault: true`
issyl0 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some of these new ones that fail RuboCop in the code in this gem: should we put them in here, the global config for the gem and the one that all its downstream consumers use, or should we put them in
.rubocop.yml
inside this repo only?I guess I'm now concerned, after @bensheldon's comments, about this gem's config not being a reflection of the styleguide? Who gets to make decisions on what we include in the styleguide, and hence who gets to "control" what sensible default RuboCop configuration we send out into the world?