no-unused-fragments

Since 0.9.0 · In the rulesets: Recommended at error, Strict at error, All at error

This rule checks that every fragment is spread by an operation, directly or through other fragments, 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 no-unused-fragments 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.

query Q { user { ...A } }
fragment A on User { id }

Bad. The linter reports Fragment "A" is never used..

query Q { user { id } }
fragment A on User { id }

Turn it off or change its severity

In apigenie.yaml, off turns the rule off and warning or error sets its severity; a rule with options takes the severity and the options as a pair, [warning, options]. lint.graphql has the details.

commands:
  lint:
    graphql:
      rules:
        no-unused-fragments: off

Further reading

Last updated on View as Markdown
Was this helpful?