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 56
  • Vulnerability1
  • Bug12
  • Security Hotspot3
  • Code Smell40
 
Tags
    Impact
      Clean code attribute
        1. URLs of Salesforce pages should be relative, not absolute.

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

           Bug
        3. DML statements should not be used inside loops

           Bug
        4. Record IDs should not be hardcoded

           Bug
        5. Triggers should process records in bulk

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

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

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

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

           Bug
        10. All code should be reachable

           Bug
        11. Variables should not be self-assigned

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

           Bug

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

        intentionality - clear
        reliability
        Bug

          Why is this an issue?

          Using operator pairs (=+, =-, or =!) that look like reversed single operators (+=, -= or !=) is confusing. They compile and run but do not produce the same result as their mirrored counterpart.

          Integer target = -5;
          Integer num = 3;
          
          target =- num;  // Noncompliant: target = -3. Is that the expected behavior?
          target =+ num; // Noncompliant: target = 3
          

          This rule raises an issue when =+, =-, or =! are used without any space between the operators and when there is at least one whitespace after.

          Replace the operators with a single one if that is the intention.

          Integer target = -5;
          Integer num = 3;
          
          target -= num;  // target = -8
          

          Or fix the spacing to avoid confusion

          Integer target = -5;
          Integer num = 3;
          
          target = -num;  // target = -3
          
            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

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use