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
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

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

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
Filtered: 8 rules found
brain-overload
    Impact
      Clean code attribute
        1. Cognitive Complexity of functions should not be too high

           Code Smell
        2. "switch" statements should not have too many "case" clauses

           Code Smell
        3. Functions and methods should not have too many lines

           Code Smell
        4. Control flow statements "if", "for" and "switch" should not be nested too deeply

           Code Smell
        5. "switch case" clauses should not have too many lines

           Code Smell
        6. Functions should not have too many parameters

           Code Smell
        7. Expressions should not be too complex

           Code Smell
        8. Files should not have too many lines of code

           Code Smell

        Functions should not have too many parameters

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        Functions with a long parameter list are difficult to use because maintainers must figure out the role of each parameter and keep track of their position.

        func setCoordinates(x1 int, y1 int, z1 int, x2 int, y2 int, z2 int) { // Noncompliant
            // ...
        }
        

        The solution can be to:

        • Split the function into smaller ones
        // Each function does a part of what the original setCoordinates function was doing, so confusion risks are lower
        func setOrigin(x int, y int, z int) {
           // ...
        }
        
        func setSize(width int, height int, depth int) {
           // ...
        }
        
        • Find a better data structure for the parameters that group data in a way that makes sense for the specific application domain
        type point struct { // In geometry, Point is a logical structure to group data
            x int
            y int
            z int
        }
        
        func setCoordinates(p1 point, p2 point) {
            // ...
        }
        

        This rule raises an issue when a function has more parameters than the provided threshold.

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use