no-fragment-cycles

Since 0.9.0

This rule checks that fragments don’t spread themselves, directly or indirectly, 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.

Configuration

This rule has no options.

version: "1.0"
commands:
  lint:
    graphql:
      rules:
        no-fragment-cycles: warning

The rule can be disabled for a node and everything nested in it with an # apigenie-lint-disable no-fragment-cycles comment on the node, or for a whole file with the comment at the top of the file, separated from the first definition by a blank line. It applies to operations and fragments.

Examples

Good.

fragment A on User { id }

Bad. The linter reports Cannot spread fragment "A" within itself via "B"..

fragment A on User { ...B }
fragment B on User { ...A }

Further reading

• GraphQL specification