known-argument-names
Since 0.9.0 · In the rulesets: Recommended at error, Strict at error, All at error
This rule checks that the arguments given to fields and directives are defined by them.
Rule details
Unknown arguments are rejected by the server. The arguments of @skip, @include and of the directives of the schema are checked.
The rule checks operations against the schema files named by the schema property of the
configuration, or against the type system of their own document. It reports nothing without a
schema.
The rule applies to operations and fragments. An # apigenie-lint-disable known-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 User { user(id: 1) { id } }
Bad. The linter reports Unknown argument "userId" on field "Query.user"..
query User { user(userId: 1) { 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:
known-argument-names: off