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: 3 rules found
bad-practice
    Impact
      Clean code attribute
        1. "@override" should be used on overriding members

           Code Smell
        2. Deprecated elements should include explanation

           Code Smell
        3. Standard outputs should not be used directly to log anything

           Code Smell

        "@override" should be used on overriding members

        intentionality - clear
        maintainability
        Code Smell
        • bad-practice

        Why is this an issue?

        More Info

        While not mandatory, using the @override annotation on compliant members (methods, properties, operators) improves readability by making it explicit that members are overridden.

        Unlike other languages, all methods in Dart are virtual by default. So, using the @override annotation prevents accidental overriding of a base class method in a subclass.

        Noncompliant code example

        class ParentClass {
          bool doSomething(){/*...*/}
        }
        class FirstChildClass extends ParentClass {
          bool doSomething(){/*...*/}  // Noncompliant
        }
        

        Compliant solution

        class ParentClass {
          bool doSomething(){/*...*/}
        }
        class FirstChildClass extends ParentClass {
          @override
          bool doSomething(){/*...*/}  // Compliant
        }
        
          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