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
Dart

Dart static code analysis

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

  • All rules 126
  • Vulnerability4
  • Bug15
  • Security Hotspot8
  • Code Smell99
Filtered: 2 rules found
pitfall
    Impact
      Clean code attribute
        1. Constant patterns should not be used with type literals

           Bug
        2. Control structures should use curly braces

           Code Smell

        Control structures should use curly braces

        intentionality - clear
        maintainability
        Code Smell
        • pitfall

        Control structures are code statements that impact the program’s control flow (e.g., if statements, for loops, etc.)

        Why is this an issue?

        More Info

        While not technically incorrect, the omission of curly braces can be misleading and may lead to the introduction of errors during maintenance.

        In the following example, the two calls seem to be attached to the if statement, but only the first one is, and checkSomething will always be executed:

        if (condition)  // Noncompliant
          executeSomething();
          checkSomething();
        

        Adding curly braces improves the code readability and its robustness:

        if (condition) {
          executeSomething();
          checkSomething();
        }
        

        The rule raises an issue when a control structure has no curly braces.

        Exceptions

        The rule does not apply to single-line if statements. It does apply, however, to single-line for, while and do while statements.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.7

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use