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

        Class names should comply with a naming convention

        consistency - identifiable
        maintainability
        Code Smell
        • convention

        Why is this an issue?

        Shared naming conventions allow teams to collaborate efficiently.

        This rule raises an issue when a class name does not match a provided regular expression.

        For example, with the default provided regular expression ^[A-Z][a-zA-Z0-9]*$, the class:

        class myClass {} // Noncompliant
        

        should be renamed to

        class MyClass {}
        
          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