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
Flex

Flex static code analysis

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

  • All rules 76
  • Vulnerability5
  • Bug9
  • Security Hotspot1
  • Code Smell61
 
Tags
    Impact
      Clean code attribute
        1. All branches in a conditional structure should not have exactly the same implementation

           Bug
        2. Cases in a "switch" should not have the same condition

           Bug
        3. Method visibility should be explicitly declared

           Bug
        4. Classes that extend "Event" should override "Event.clone()"

           Bug
        5. Constructors should not dispatch events

           Bug
        6. "ManagedEvents" tags should have companion "Event" tags

           Bug
        7. Multiple "++" or "--" unary operators should not be used in a single arithmetic expression

           Bug
        8. "with" statements should not be used

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

           Bug

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

        Bug

          This rule is deprecated, and will eventually be removed.

          Why is this an issue?

          More Info

          if statements with conditions that are always false have the effect of making blocks of code non-functional. if statements with conditions that are always true are completely redundant, and make the code less readable.

          There are three possible causes for the presence of such code:

          • An if statement was changed during debugging and that debug code has been committed.
          • Some value was left unset.
          • Some logic is not doing what the programmer thought it did.

          In any of these cases, unconditional if statements should be removed.

          Noncompliant code example

          if (true) {
            doSomething();
          }
          ...
          if (false) {
            doSomethingElse();
          }
          

          Compliant solution

          doSomething();
          ...
          
            Available In:
          • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
          • SonarQube Community BuildAnalyze code in your
            on-premise CI
            Available Since
            9.1
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Developer Edition
            Available Since
            9.1

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use