no-deprecated
Since 0.9.0 · In the rulesets: Recommended at error, Strict at error, All at error
This rule checks that operations don’t use deprecated fields, arguments and enum values.
Rule details
Deprecated elements will be removed from the schema; operations using them will break. The message includes the reason of the deprecation.
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 no-deprecated 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 { name } }
Bad. The linter reports The field 'User.login' is deprecated: Use name..
query Me { me { login } }
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:
no-deprecated: off