operation-name-defined

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

This rule checks that operations have names.

Rule details

Names identify operations in server logs, metrics, persisted queries and developer tools.

The rule applies to operations and fragments. An # apigenie-lint-disable operation-name-defined 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 Me { me { id } }

Bad. The linter reports The query should have a name.

{ me { 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:
        operation-name-defined: off

Related rules

Was this helpful?