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
error-handling
    Impact
      Clean code attribute
        1. Exceptions should not be ignored

           Code Smell
        2. Jump statements should not occur in "finally" blocks

           Bug

        Jump statements should not occur in "finally" blocks

        intentionality - logical
        reliability
        Bug
        • cwe
        • error-handling

        Why is this an issue?

        More Info

        Using return, break, or continue from a finally block suppresses the propagation of any unhandled Exception which was thrown in the try or catch block.

        This rule raises an issue when a jump statement (break, continue, return) would force control flow to leave a finally block.

        Noncompliant code example

        class ReturnInFinally {
          int nonCompliantMethod(int n) {
            for (int i = 0; i < n; ++i) {
              try {
                functionThrowingException(i);
              } catch (e) {
                print(e);
              } finally {
                return 1; // Noncompliant
              }
            }
            return 0;
          }
        }
        
        class ContinueInFinally {
          int nonCompliantMethod(int n) {
            for (int i = 0; i < n; ++i) {
              try {
                functionThrowingException(i);
              } catch (e) {
                print(e);
              } finally {
                continue; // Noncompliant
              }
            }
            return 0;
          }
        }
        
        class BreakInFinally {
          int nonCompliantMethod(int n) {
            for (int i = 0; i < n; ++i) {
              try {
                functionThrowingException(i);
              } catch (e) {
                print(e);
              } finally {
                break; // Noncompliant
              }
            }
            return 0;
          }
        }
        

        Compliant solution

        class Ok {
          int nonCompliantMethod(int n) {
            for (int i = 0; i < n; ++i) {
              try {
                functionThrowingException(i);
              } catch (e) {
                print(e);
                return 1;
              }
            }
            return 0;
          }
        }
        
          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