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
Filtered: 8 rules found
brain-overload
    Impact
      Clean code attribute
        1. Cognitive Complexity of functions should not be too high

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

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

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

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

           Code Smell
        6. Functions should not have too many parameters

           Code Smell
        7. Expressions should not be too complex

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

           Code Smell

        Expressions should not be too complex

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        The complexity of an expression is defined by the number of &&, || and condition ? ifTrue : ifFalse operators it contains.

        A single expression’s complexity should not become too high to keep the code readable.

        Noncompliant code example

        With the default threshold value of 3:

        if ((condition1 && condition2) || (condition3 && condition4)) && condition5
          ...
        end
        

        Compliant solution

        if (myFirstCondition() || mySecondCondition()) && myLastCondition()
          ...
        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