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
 
Tags
    Impact
      Clean code attribute
        1. Apex classes should contain at most one "@InvocableMethod" annotation

           Bug
        2. DML operations in catch blocks can mask original exceptions

           Bug
        3. Future methods must be static and return void

           Bug
        4. Test classes should have only one @testSetup method

           Bug
        5. Methods with "@AuraEnabled" should be public or global

           Bug
        6. Classes implementing "Database.Batchable" should be declared as "global"

           Bug
        7. Future methods making HTTP callouts should include "callout=true" parameter

           Bug
        8. Future methods should not call other future methods

           Bug
        9. SOQL queries should include LIMIT clauses to prevent hitting governor limits

           Bug
        10. SOQL queries should be assigned to Lists to avoid QueryException

           Bug
        11. Test methods should not have parameters

           Bug
        12. URLs should not be hardcoded in Apex code

           Bug
        13. "@future" methods should not be called in loops

           Bug
        14. Email messages should be sent in batches

           Bug
        15. URLs of Salesforce pages should be relative, not absolute.

           Bug
        16. "getRecordTypeInfosByDeveloperName()" should be used instead of "getRecordTypeInfosByName()"

           Bug
        17. DML statements should not be used inside loops

           Bug
        18. Record IDs should not be hardcoded

           Bug
        19. Triggers should process records in bulk

           Bug
        20. All branches in a conditional structure should not have exactly the same implementation

           Bug
        21. Non-existent operators like "=+" should not be used

           Bug
        22. Related "if"/"else if" statements and "when" in a "switch" should not have the same condition

           Bug
        23. Identical expressions should not be used on both sides of a binary operator

           Bug
        24. All code should be reachable

           Bug
        25. Variables should not be self-assigned

           Bug
        26. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug

        Related "if"/"else if" statements and "when" in a "switch" should not have the same condition

        intentionality - logical
        reliability
        Bug
        • unused
        • pitfall

        Why is this an issue?

        A switch and a chain of if/else if statements is evaluated from top to bottom. At most, only one branch will be executed: the first one with a condition that evaluates to true.

        Therefore, duplicating a condition automatically leads to dead code. Usually, this is due to a copy/paste error. At best, it’s simply dead code and at worst, it’s a bug that is likely to induce further bugs as the code is maintained, and obviously it could lead to unexpected behavior.

        For a switch, the second when will never be executed, rendering it dead code. Worse there is the risk in this situation that future maintenance will be done on the dead case, rather than on the one that’s actually used.

        Noncompliant code example

        if (param == 1) {
          openWindow();
        } else if (param == 2) {
          closeWindow();
        } else if (param == 1) { // Noncompliant
          moveWindowToTheBackground();
        }
        
        switch on i {
          when 1 {
            // ...
          }
          when 2 {
            // ...
          }
          when 1 { // Noncompliant
            // ...
          }
          when else {
            // ...
          }
        }
        

        Compliant solution

        if (param == 1) {
          openWindow();
        } else if (param == 2) {
          closeWindow();
        } else if (param == 3) {
          moveWindowToTheBackground();
        }
        
        switch on i {
          when 1 {
            // ...
          }
          when 2 {
            // ...
          }
          when else {
            // ...
          }
        }
        
          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 ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          9.1

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use