SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Ruby

Ruby static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your RUBY code

  • All rules 42
  • Bug7
  • Security Hotspot2
  • Code Smell33
 
Tags
    Impact
      Clean code attribute
        1. Multi-line comments should not be empty

           Code Smell
        2. Methods should not have identical implementations

           Code Smell
        3. All branches in a conditional structure should not have exactly the same implementation

           Bug
        4. Cognitive Complexity of functions should not be too high

           Code Smell
        5. Non-existent operators like "=+" should not be used

           Bug
        6. Ruby parser failure

           Code Smell
        7. Hard-coded credentials are security-sensitive

           Security Hotspot
        8. Boolean checks should not be inverted

           Code Smell
        9. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        10. Related "if/elsif" statements and "when" in a "case" should not have the same condition

           Bug
        11. "case" statements should not be nested

           Code Smell
        12. Identical expressions should not be used on both sides of a binary operator

           Bug
        13. All code should be reachable

           Bug
        14. Variables should not be self-assigned

           Bug
        15. Unused local variables should be removed

           Code Smell
        16. "case" statements should not have too many "when" clauses

           Code Smell
        17. Track lack of copyright and license headers

           Code Smell
        18. Functions should not have too many lines of code

           Code Smell
        19. Control flow statements "if", "for", "while", "until", "case" and "begin...rescue" should not be nested too deeply

           Code Smell
        20. Octal values should not be used

           Code Smell
        21. Using hardcoded IP addresses is security-sensitive

           Security Hotspot
        22. "case" statements should have "else" clauses

           Code Smell
        23. "if ... else if" constructs should end with "else" clauses

           Code Smell
        24. Statements should be on separate lines

           Code Smell
        25. String literals should not be duplicated

           Code Smell
        26. Methods should not be empty

           Code Smell
        27. Unused function parameters should be removed

           Code Smell
        28. Function and block parameter names should comply with a naming convention

           Code Smell
        29. "case when" clauses should not have too many lines of code

           Code Smell
        30. Useless "if true ..." and "if false ..." blocks should be removed

           Bug
        31. Track uses of "TODO" tags

           Code Smell
        32. Track uses of "FIXME" tags

           Code Smell
        33. Redundant pairs of parentheses should be removed

           Code Smell
        34. Nested blocks of code should not be left empty

           Code Smell
        35. Functions should not have too many parameters

           Code Smell
        36. Expressions should not be too complex

           Code Smell
        37. Mergeable "if" statements should be combined

           Code Smell
        38. Tabulation characters should not be used

           Code Smell
        39. Files should not have too many lines of code

           Code Smell
        40. Lines should not be too long

           Code Smell
        41. Class names should comply with a naming convention

           Code Smell
        42. Method names should comply with a naming convention

           Code Smell

        "case when" clauses should not have too many lines of code

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        The case statement should be used only to clearly define some new branches in the control flow. As soon as a when clause contains too many statements this highly decreases the readability of the overall control flow statement. In such case, the content of the case clause should be extracted into a dedicated function.

        Noncompliant code example

        With the threshold set at 5:

        case myVariable
        when 0 then # Noncompliant: 6 lines till next "when"
            methodCall1("")
            methodCall2("")
            methodCall3("")
            methodCall4("")
            methodCall5("")
            methodCall6("")
        when 1
           # ...
        end
        

        Compliant solution

        case myVariable
        when 0 then
          doSomething()
        when 1
           # ...
        end
        ...
        def doSomething()
            methodCall1("")
            methodCall2("")
            methodCall3("")
            methodCall4("")
            methodCall5("")
            methodCall6("")
        end
        
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use