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
Apex

Apex static code analysis

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

  • All rules 97
  • Vulnerability2
  • Bug26
  • Security Hotspot3
  • Code Smell66
Filtered: 13 rules found
convention
    Impact
      Clean code attribute
        1. Custom exception classes should follow proper naming conventions

           Code Smell
        2. Loops should use braces

           Code Smell
        3. Constants should use SNAKE_CASE with all uppercase letters

           Code Smell
        4. Apex classes and methods should have explicit access modifiers

           Code Smell
        5. Test classes should be annotated with "@isTest"

           Code Smell
        6. Custom event names should not be prefixed with "on"

           Code Smell
        7. Track lack of copyright and license headers

           Code Smell
        8. Statements should be on separate lines

           Code Smell
        9. Local variable and method parameter names should comply with a naming convention

           Code Smell
        10. Tabulation characters should not be used

           Code Smell
        11. Lines should not be too long

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

           Code Smell
        13. Function names should comply with a naming convention

           Code Smell

        Loops should use braces

        consistency - conventional
        reliability
        maintainability
        Code Smell
        • convention
        • formatting

        This rule raises an issue when a loop does not use braces to enclose its body, even if the body contains only a single statement.

        Why is this an issue?

        How can I fix it?

        More Info

        Loops without braces can lead to maintenance issues and bugs. When the loop body contains only one statement, it’s tempting to omit the braces for brevity.

        However, this practice creates several problems:

        • Accidental logic errors: When developers later add statements after the loop, they might assume these new statements are part of the loop body. Without braces, only the first statement actually belongs to the loop.
        • Reduced readability: Braces make the loop structure immediately clear to anyone reading the code.
        • Inconsistent formatting: Different developers might format single-statement loops differently, making the codebase harder to maintain.

        Consider this example:

        while (i < items.size())
            processItem(items[i]);
            i++; // This line is NOT part of the loop!
        

        In this case, the increment statement runs only once after the loop completes, creating an infinite loop. With braces, this mistake would be immediately obvious.

        What is the potential impact?

        This issue can lead to logic errors and infinite loops when developers mistakenly add statements they believe are part of the loop body. It also reduces code maintainability and consistency across the codebase.

          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