Hello there. I assume some of you fond RuboCop is too fussy about the rules. We have developed rubocop.yml files that prioritize developing speed to the rules.
You can have a try!
This is about optimization and configuration of Rubocop which focuses on “finding codes which lead to the bug”.
By place the rubocop.yml file in the top of the directory of repository, SideCI will follow the configuration for the verification and provide you comments. It would be good for those who use just RuboCop rather than SideCI.
Table Of Contents
- Use RuboCop effectively and suppress bugs
- Enable Lint cops by default
- Lintcops to be disabled exceptionally
- Disable Style cops by default
- Style cops to be enabled exceptionally
- Other cops
.rubocop.ymlwith above understanding- “I still have many violations!” when you’d like to perform only simple verification even more effectively
- Summary
Use RuboCop effectively and suppress bugs
「RuboCop」 is a static analytical tool for Ruby.
Although RuboCop is assumed for a coding verification tool, you can use it as “a tool that finds codes which lead to the bug”.
But, you will have many violations if you use RuboCop for Rails application development with default configuration.
With such conditions, the violation which will be a bug won’t be recognized either.
Here, we shall configure .rubocop.yml to enable only the cop which finds the violation to be a bug.
Enable Lint cops by default
The term “cop” is the rules to verify the codes in RuboCop.
Lint cops are the one which detects the codes which may cause bugs.
In README of RuboCop, it describes that disabling Lint cops is a ”bad idea”.
For example, below Ruby code has a bug, but even a programmer many not recognize it immediately.
def raises_sometimes(value)
if value == 1
raise '1 is bad value!'
elif value == 2
raise '2 is bad value, too!'
end
endLint cops can indirectly detect the place that may have bugs.
You can verify only Lint cop by -l/--lint option (surely you can also verify without this option).
I execute here.
rubocop test.rb --lint
Inspecting 1 file
WOffenses:test.rb:4:5: W: Lint/UnreachableCode: Unreachable code detected.
elif value == 2
^^^^^^^^^^^^^^^1 file inspected, 1 offense detectedSince elif is not in ruby(it should be elseif), the rows after raise is detected as UnreachableCode(unreachable).
In this example, since it is fine for the syntax of Ruby, it can’t be detected by ruby -c.
Since it may detect such violations, we shall enable Lint cops.
Lintcops to be disabled exceptionally
Following 2 cops are assumed that exceptionally won’t contribute the detection of bugs which influence immediately.
Lint/DeprecatedClassMethods
It detects depreciated methods such as File.exists?.
Although it is better not to use deprecated methods, it doesn’t cause bugs immediately.
Lint/StringConversionInInterpolation
It detects the place which is calling extra #to_s.
Again, it is better not to call unnecessary methods, but it doesn’t cause bugs immediately
For above 2 cops, we shall disable in .rubocop.yml file of this entry exceptionally.
Disable Style cops by default
As mentioned earlier, you will have many violations if you use RuboCop for Rails application development with default configuration..
Most of the case the cop for Style doesn’t contribute to detect bugs, you can disable it.
Style cops to be enabled exceptionally
For exceptional cases, the following 3 Style cops may contribute to detect the bugs.
Style/AndOr
Cop that recommends && over and, and || over or. and and && have a different binding priority.
Since this is a bit complicated, I explain by using this easy-to-understand description article.
if true and false
puts "1: true"
else
puts "1: false"
end
#=> 1: falseThe code is not so surprising, but it produces a surprising result when combined with (=).
true_and_false = true and false
if true_and_false
puts "2: true"
else
puts "2: false"
end
#=> 2: trueTo prevent this bug, it is useful to use && and ||.
Style/CaseEquality
A cop that restricts the usage of ===.
=== is used in the Case format and it might operate differently as expected so this cop will be of use.
Style/GlobalVars
A cop that restricts the use of global variables.
Global variable might operate differently as expected.
Those 3 Style cops mentioned above to be enabled in the .rubocop.yml of this entry.
Other cops
Other cops follow the below.
- Disable Metrics cops, since those are more related to clean codes.
*Enable Performance cops, since the number of cops is less and it may detect the issue of efficiency. - Enable Rails cops, although some are related to Style but the number is less and it detects the date and time(
Rails/DateandRails/TimeZone) items.
.rubocop.yml with above understanding
With above understanding, now the .rubocop.yml is as shown in below.
Since most of Style cops are disabled, you will have much less violations.
Please rename the file to .rubocop.yml when downloading the file from the link above.
AllCops:
Exclude:
- 'vendor/**/*'
RunRailsCops: true
DisplayCopNames: trueStyle/AccessModifierIndentation:
Enabled: falseStyle/AccessorMethodName:
Enabled: falseStyle/Alias:
Enabled: falseStyle/AlignArray:
Enabled: falseStyle/AlignHash:
Enabled: falseStyle/AlignParameters:
Enabled: falseStyle/AndOr:
Enabled: trueStyle/ArrayJoin:
Enabled: falseStyle/AsciiComments:
Enabled: falseStyle/AsciiIdentifiers:
Enabled: falseStyle/Attr:
Enabled: falseStyle/BeginBlock:
Enabled: falseStyle/BarePercentLiterals:
Enabled: falseStyle/BlockComments:
Enabled: falseStyle/BlockEndNewline:
Enabled: falseStyle/Blocks:
Enabled: falseStyle/BracesAroundHashParameters:
Enabled: falseStyle/CaseEquality:
Enabled: trueStyle/CaseIndentation:
Enabled: falseStyle/CharacterLiteral:
Enabled: falseStyle/ClassAndModuleCamelCase:
Enabled: falseStyle/ClassAndModuleChildren:
Enabled: falseStyle/ClassCheck:
Enabled: falseStyle/ClassMethods:
Enabled: falseStyle/ClassVars:
Enabled: falseStyle/ColonMethodCall:
Enabled: falseStyle/CommentAnnotation:
Enabled: falseStyle/CommentIndentation:
Enabled: falseStyle/ConstantName:
Enabled: falseStyle/DefWithParentheses:
Enabled: falseStyle/DeprecatedHashMethods:
Enabled: falseStyle/Documentation:
Enabled: falseStyle/DotPosition:
Enabled: falseStyle/DoubleNegation:
Enabled: falseStyle/EachWithObject:
Enabled: falseStyle/ElseAlignment:
Enabled: falseStyle/EmptyElse:
Enabled: falseStyle/EmptyLineBetweenDefs:
Enabled: falseStyle/EmptyLines:
Enabled: falseStyle/EmptyLinesAroundAccessModifier:
Enabled: falseStyle/EmptyLinesAroundBlockBody:
Enabled: falseStyle/EmptyLinesAroundClassBody:
Enabled: falseStyle/EmptyLinesAroundModuleBody:
Enabled: falseStyle/EmptyLinesAroundMethodBody:
Enabled: falseStyle/EmptyLiteral:
Enabled: falseStyle/EndBlock:
Enabled: falseStyle/EndOfLine:
Enabled: falseStyle/EvenOdd:
Enabled: falseStyle/FileName:
Enabled: falseStyle/FirstParameterIndentation:
Enabled: falseStyle/FlipFlop:
Enabled: falseStyle/For:
Enabled: falseStyle/FormatString:
Enabled: falseStyle/GlobalVars:
Enabled: trueStyle/GuardClause:
Enabled: falseStyle/HashSyntax:
Enabled: falseStyle/IfUnlessModifier:
Enabled: falseStyle/IfWithSemicolon:
Enabled: falseStyle/IndentationConsistency:
Enabled: falseStyle/IndentationWidth:
Enabled: falseStyle/IndentArray:
Enabled: falseStyle/IndentHash:
Enabled: falseStyle/InfiniteLoop:
Enabled: falseStyle/Lambda:
Enabled: falseStyle/LambdaCall:
Enabled: falseStyle/LeadingCommentSpace:
Enabled: falseStyle/LineEndConcatenation:
Enabled: falseStyle/MethodCallParentheses:
Enabled: falseStyle/MethodDefParentheses:
Enabled: falseStyle/MethodName:
Enabled: falseStyle/ModuleFunction:
Enabled: falseStyle/MultilineBlockChain:
Enabled: falseStyle/MultilineBlockLayout:
Enabled: falseStyle/MultilineIfThen:
Enabled: falseStyle/MultilineOperationIndentation:
Enabled: falseStyle/MultilineTernaryOperator:
Enabled: falseStyle/NegatedIf:
Enabled: falseStyle/NegatedWhile:
Enabled: falseStyle/NestedTernaryOperator:
Enabled: falseStyle/Next:
Enabled: falseStyle/NilComparison:
Enabled: falseStyle/NonNilCheck:
Enabled: falseStyle/Not:
Enabled: falseStyle/NumericLiterals:
Enabled: falseStyle/OneLineConditional:
Enabled: falseStyle/OpMethod:
Enabled: falseStyle/ParenthesesAroundCondition:
Enabled: falseStyle/PercentLiteralDelimiters:
Enabled: falseStyle/PercentQLiterals:
Enabled: falseStyle/PerlBackrefs:
Enabled: falseStyle/PredicateName:
Enabled: falseStyle/Proc:
Enabled: falseStyle/RaiseArgs:
Enabled: falseStyle/RedundantBegin:
Enabled: falseStyle/RedundantException:
Enabled: falseStyle/RedundantReturn:
Enabled: falseStyle/RedundantSelf:
Enabled: falseStyle/RegexpLiteral:
Enabled: falseStyle/RescueModifier:
Enabled: falseStyle/SelfAssignment:
Enabled: falseStyle/Semicolon:
Enabled: falseStyle/SignalException:
Enabled: falseStyle/SingleLineBlockParams:
Enabled: falseStyle/SingleLineMethods:
Enabled: falseStyle/SingleSpaceBeforeFirstArg:
Enabled: falseStyle/SpaceAfterColon:
Enabled: falseStyle/SpaceAfterComma:
Enabled: falseStyle/SpaceAfterControlKeyword:
Enabled: falseStyle/SpaceAfterMethodName:
Enabled: falseStyle/SpaceAfterNot:
Enabled: falseStyle/SpaceAfterSemicolon:
Enabled: falseStyle/SpaceBeforeBlockBraces:
Enabled: falseStyle/SpaceBeforeComma:
Enabled: falseStyle/SpaceBeforeComment:
Enabled: falseStyle/SpaceBeforeSemicolon:
Enabled: falseStyle/SpaceInsideBlockBraces:
Enabled: falseStyle/SpaceAroundBlockParameters:
Enabled: falseStyle/SpaceAroundEqualsInParameterDefault:
Enabled: falseStyle/SpaceAroundOperators:
Enabled: falseStyle/SpaceBeforeModifierKeyword:
Enabled: falseStyle/SpaceInsideBrackets:
Enabled: falseStyle/SpaceInsideHashLiteralBraces:
Enabled: falseStyle/SpaceInsideParens:
Enabled: falseStyle/SpaceInsideRangeLiteral:
Enabled: falseStyle/SpecialGlobalVars:
Enabled: falseStyle/StringLiterals:
Enabled: falseStyle/StringLiteralsInInterpolation:
Enabled: falseStyle/StructInheritance:
Enabled: falseStyle/SymbolProc:
Enabled: falseStyle/Tab:
Enabled: falseStyle/TrailingBlankLines:
Enabled: falseStyle/TrailingComma:
Enabled: falseStyle/TrailingWhitespace:
Enabled: falseStyle/TrivialAccessors:
Enabled: falseStyle/UnlessElse:
Enabled: falseStyle/UnneededCapitalW:
Enabled: falseStyle/UnneededPercentQ:
Enabled: falseStyle/UnneededPercentX:
Enabled: falseStyle/VariableInterpolation:
Enabled: falseStyle/VariableName:
Enabled: falseStyle/WhenThen:
Enabled: falseStyle/WhileUntilDo:
Enabled: falseStyle/WhileUntilModifier:
Enabled: falseStyle/WordArray:
Enabled: falseLint/DeprecatedClassMethods:
Enabled: falseLint/StringConversionInInterpolation:
Enabled: falseMetrics/AbcSize:
Enabled: falseMetrics/BlockNesting:
Enabled: falseMetrics/ClassLength:
Enabled: falseMetrics/CyclomaticComplexity:
Enabled: falseMetrics/LineLength:
Enabled: falseMetrics/MethodLength:
Enabled: falseMetrics/ParameterLists:
Enabled: falseMetrics/PerceivedComplexity:
Enabled: false“I still have many violations!” when you’d like to perform only simple verification even more effectively
Based on the above .rubocop.yml rules, when execute rubocop for any 8 Rails projects (the number of stars are more than 300 and committed recently) which are published in github, the number of violation got less around 10%-50% by comparing with the default settings.
But, for large scale Rails applications, the number of violations are still more than 1000 and hard to check all.
We have selected below 4 cops which are simple yet detect the bugs well. These will help you to verify easily especially for the beginning.
Lint/Debugger
It detects whether methods for debug (p/pp/puts/print) are still remaining.
Lint/DuplicateMethods
It detects the locations which have duplicated method definition in the same class.
Lint/UnreachableCode
It detects unreachable locations .
Lint/Void
It detects the locations which have only operators, variables or literals and have done nothing.
To execute only above 4 cops, you can execute below command without having .rubocop.yml file.
$ rubocop — only Lint/Debugger,Lint/DuplicateMethods,Lint/UnreachableCode,Lint/Void
Followings are the result of executing this command to 8 Rails projects.
There are areas that are fine without fixing the violations, but it detected that there are 4 out of 8 Rails projects which require some fixing.
In case the developing Rails application is huge and difficult to fix or check all detected violations, by fixing those 4 violations lead to find bugs.
Summary
How did you find this?
In this entry, we have seen when Lint cop is useful and that importance, the example of .rubocop.yml especially important Lint cop.
When actually using RuboCop, you will need to determine enable/disable for respective cops.
For those who want to try out rubocop but have never done, since this judgment is already difficult, I sincerely suggest you to start with performing this .rubocop.yml and the last 4 cops.
More articles about RuboCop
- Trying the Rails or Lint options in RuboCop
- Using RuboCop for quick automated code reviews with Docker
- Use RuboCop to check the conformity of your Ruby code with the style guide
- Analyzing code with RuboCop on a Ruby on Rails project
- Extract Hidden Coding Styles to .rubocop.yml with Gry
- Let’s start using RuboCop! The release of MeowCop, the best configs for introducing RuboCop!
For more information about Sider, please go to our website.
