# known-fragment-names

Source: https://api-genie.dev/docs/linter/graphql/rules/known-fragment-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 fragment spreads name fragments of the document, 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 reports references to types and fragments that are not in the document only when the
configuration sets `self_contained: true`, since schemas and operations are often split across
files.

The rule applies to operations and fragments. An `# apigenie-lint-disable known-fragment-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 { user { ...A } }
fragment A on User { id }
```

**Bad**. The linter reports `Unknown fragment "A".`.

```graphql
query Q { user { ...A } }
```
