# unique-field-definition-names

Source: https://api-genie.dev/docs/linter/graphql/rules/unique-field-definition-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 field names of a type are unique across the type and its extensions, 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 definitions. An `# apigenie-lint-disable unique-field-definition-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
type User { id: ID! }
extend type User { name: String }
```

**Bad**. The linter reports `Field "User.id" can only be defined once.`.

```graphql
type User { id: ID! }
extend type User { id: ID }
```
