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 75
  • Bug17
  • Security Hotspot2
  • Code Smell56
Filtered: 4 rules found
style
    Impact
      Clean code attribute
        1. Modules should use "extend self" instead of "module_function"

           Code Smell
        2. Array and hash literals should be used instead of constructors when no parameters are needed

           Code Smell
        3. Logical operators "and" and "or" should be replaced with "&&" and "||"

           Code Smell
        4. Explicit RuntimeErrors should be omitted in raise statements

           Code Smell

        Array and hash literals should be used instead of constructors when no parameters are needed

        consistency - conventional
        maintainability
        Code Smell
        • convention
        • style
        • readability

        This rule raises an issue when Array.new or Hash.new is used without parameters to create empty collections.

        Why is this an issue?

        How can I fix it?

        More Info

        Using constructor methods like Array.new and Hash.new without parameters is unnecessarily verbose compared to the literal syntax [] and {}. The literal syntax is more concise, widely recognized as idiomatic Ruby, and preferred by the Ruby community.

        Literal syntax makes the code more readable and consistent with Ruby conventions. When no parameters are needed, the constructor methods provide no additional functionality over literals, making them redundant.

        This pattern is particularly important in Ruby codebases where consistency and readability are valued. Most Ruby style guides, including those from major organizations, recommend using literal syntax for empty collections.

        What is the potential impact?

        This issue affects code readability and maintainability. While it doesn’t impact functionality, inconsistent style can make code harder to read and maintain, especially in team environments where coding standards matter.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use