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: 4 rules found
suspicious
    Impact
      Clean code attribute
        1. Parameter names should match base declaration

           Code Smell
        2. "switch" statements should cover all cases

           Code Smell
        3. Exceptions should not be ignored

           Code Smell
        4. Dart build, compiler, or analyzer configuration errors

           Code Smell

        Parameter names should match base declaration

        consistency - identifiable
        maintainability
        Code Smell
        • suspicious

        Why is this an issue?

        More Info

        Parameters are part of the method signature and its identity.

        Overriding a method and changing one of its parameters' names will confuse and impact the method’s readability. In dart doc the consequences might be even worse. If an overriding method doesn’t provide ots own documentation comment, it will inherit a comment from an overridden method. If the inherited comment contains a link to the parameter, which was renamed, linking will fail.

        abstract class BankAccount
        {
          void addMoney(int money);
        }
        
        class MyBankAccount extends BankAccount
        {
          void addMoney(int amount) // Noncompliant: parameter's name differs from base
          {
            // ...
          }
        }
        

        To avoid any ambiguity in the code, a parameter’s name should match the initial declaration, whether its initial declaration is from an interface, a base class, or a partial method.

        abstract class BankAccount
        {
          void addMoney(int money);
        }
        
        class MyBankAccount extends BankAccount
        {
          void addMoney(int money)
          {
            // ...
          }
        }
        
          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