input-no-circular-non-null

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

This rule checks that input object types don’t reference themselves through non-null fields.

Rule details

No value can satisfy an input object type that requires itself, directly or through other input types, through non-null fields; the specification forbids it. Nullable and list fields break the cycle.

The rule applies to definitions. An # apigenie-lint-disable input-no-circular-non-null 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.

input Filter { and: [Filter!], not: Filter }

Bad. The linter reports Cannot reference Input Object "Filter" within itself through a series of non-null fields: "not"..

input Filter { not: Filter! }

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:
        input-no-circular-non-null: off

Further reading

Last updated on View as Markdown
Was this helpful?