.rubocop.yml in breakers-0.2.3 vs .rubocop.yml in breakers-0.2.4
- old
+ new
@@ -1,9 +1,11 @@
AllCops:
TargetRubyVersion: 2.3
Include:
- 'Rakefile'
+ Exclude:
+ - Gemfile
Metrics/LineLength:
Max: 140
# Removes the requirement for using double quotes only for string interpolation.
@@ -20,10 +22,13 @@
Max: 230
Metrics/MethodLength:
Max: 50
+Metrics/BlockLength:
+ Max: 500
+
Metrics/AbcSize:
Max: 75
Metrics/CyclomaticComplexity:
Max: 20
@@ -96,11 +101,11 @@
# iteration rather than using an if block that runs to the end of the loop, and it suffers from the same
# problems as above.
Style/Next:
Enabled: false
-Style/IndentArray:
+Layout/IndentArray:
EnforcedStyle: consistent
# This forces you to change simple if/unless blocks to the conditional form like: `return 2 if badness`.
# Unfortunately there are a number of cases where it makes sense to use the block form even for simple statements,
# and the modifier form can be easy to miss when scanning code.
@@ -147,11 +152,11 @@
Style/WordArray:
MinSize: 5
# Some people really like to put lines at the beginning and end of class bodies, while other people
# really don't. It doesn't really seem to matter.
-Style/EmptyLinesAroundClassBody:
+Layout/EmptyLinesAroundClassBody:
Enabled: false
# This forces you to put a comment like this at the top of every single file:
# frozen_string_literal: true
# In Ruby 3, string literals will be frozen by default, so doing so future-proofs
@@ -162,14 +167,14 @@
# this forces you to use the lambda keyword rather than -> for multiline lambdas, which seems totally arbitrary
Style/Lambda:
Enabled: false
# Force indentation for milti-line expressions and method calls
-Style/MultilineOperationIndentation:
+Layout/MultilineOperationIndentation:
EnforcedStyle: indented
-Style/MultilineMethodCallIndentation:
+Layout/MultilineMethodCallIndentation:
EnforcedStyle: indented
# This disallows the use of $1, $2 from regular expressions, which seems to make no sense whatsoever
Style/PerlBackrefs:
Enabled: false
@@ -196,10 +201,10 @@
# Enforce alignment of multi-line assignments to be like this:
# variable = if test
# ...
# end
Lint/EndAlignment:
- AlignWith: variable
+ EnforcedStyleAlignWith: variable
# This cop will require you to replace or prefix method arguments that go unused with underscores. The problem
# is that while seeming to solve no problem this could easily cause issues where someone editing the code to
# begin using the variable forgets to remove the underscore. Also, if you replace the argument with _, then
# information about the meaning of that argument is lost.