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: 9 rules found
clumsy
    Impact
      Clean code attribute
        1. Interpolation should be used instead of String concatenation

           Code Smell
        2. Collection literals should be preferred

           Code Smell
        3. Conditional assignment should be preferred

           Code Smell
        4. Iterable "whereType" should be used to filter by type

           Code Smell
        5. "this" should only be used when required

           Code Smell
        6. Variables should not be initialized with "null"

           Code Smell
        7. "is!" should be used instead of "!(. is .)"

           Code Smell
        8. Overriding methods should do more than simply call the same method in the super class

           Code Smell
        9. "isEmpty" or "isNotEmpty" should be used to test for emptiness

           Code Smell

        "is!" should be used instead of "!(. is .)"

        intentionality - clear
        maintainability
        Code Smell
        • clumsy

        Why is this an issue?

        More Info

        is! operator is used to check if an object is not of a specified type. While x is! Y is an equivalent of !(x is Y), it is preferred to use the first one. The x is! Y syntax is more compact and more readable than the !(x is Y) syntax. It is also less error-prone when used in complex expressions.

        Noncompliant code example

        if (!(x is Y)) {
          print("$x is not Y!")
        }
        

        Compliant solution

        if (x is! Y) {
          print("$x is not Y!")
        }
        
          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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use