# unique-variable-names

Source: https://apigenie.pl/docs/linter/graphql/rules/unique-variable-names

A rule of the GraphQL linter, which reads GraphQL schemas and operations. Since 0.9.0. In the rulesets: Recommended at error, Strict at error, All at error.

This rule checks that the variable names of an operation are unique, as the GraphQL specification requires.

## Rule details

The rule reports the issues of the validation rule of the same name, with the messages of graphql-js. A document that breaks it is rejected by GraphQL servers and tools, so the rule should stay enabled with the `error` severity.

The rule applies to operations and fragments. An `# apigenie-lint-disable unique-variable-names`
comment on a node turns it off for the node and everything nested in it; at the top of the file,
separated from the first definition by a blank line, the comment turns it off for the whole file.

## Examples

**Good**.

```graphql
query Q($a: Int, $b: Int) { f(a: $a, b: $b) }
```

**Bad**. The linter reports `There can be only one variable named "$a".`.

```graphql
query Q($a: Int, $a: Int) { f(a: $a) }
```
