# no-undefined-variables

Source: https://api-genie.dev/docs/linter/graphql/rules/no-undefined-variables

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 variables used by an operation, including in the fragments it spreads, are defined by the operation, 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 no-undefined-variables`
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($id: ID!) { user(id: $id) { id } }
```

**Bad**. The linter reports `Variable "$id" is not defined by operation "Q".`.

```graphql
query Q { user(id: $id) { id } }
```
