unique-argument-names

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

This rule checks that the argument names of a field or directive are unique, 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 applies to operations and fragments. An # apigenie-lint-disable unique-argument-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.

query Q { users(first: 1, after: "a") { id } }

Bad. The linter reports There can be only one argument named "first"..

query Q { users(first: 1, first: 2) { 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:
        unique-argument-names: off

Further reading

Was this helpful?