useUniqueVariableNames

GraphQL

Note

This rule has been implemented but not released yet. It will be available in the next release.

Caution

This rule is part of the nursery group. This means that it is experimental and the behavior can change at any time.

Summary

• Diagnostic Category: lint/nursery/useUniqueVariableNames
• This rule doesn’t have a fix.
• The default severity of this rule is information.
• Sources:
  • Same as @graphql-eslint/unique-variable-names

How to configure

biome.json

{
  "linter": {
    "rules": {
      "nursery": {
        "useUniqueVariableNames": "error"
      }
    }
  }
}

Description

Require all variable definitions to be unique.

A GraphQL operation is only valid if all its variables are uniquely named.

Examples

Invalid

query ($x: Int, $x: Int) {
  field
}

code-block.graphql:1:7 lint/nursery/useUniqueVariableNames ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Duplicate variable name.
  
  > 1 │ query ($x: Int, $x: Int) {
      │       ^^^^^^^^^^^^^^^^^^
    2 │   field
    3 │ }
  
  ℹ A GraphQL operation is only valid if all its variables are uniquely named. Make sure to name every variable differently.
  
  ℹ This rule belongs to the nursery group, which means it is not yet stable and may change in the future. Visit https://biomejs.dev/linter/#nursery for more information.
  

Valid

query ($x: Int, $y: Int) {
  field
}

Related links

• Disable a rule
• Configure the code fix
• Rule options
• Source Code
• Test Cases