possible-type-extensions
Since 0.9.0 · In the rulesets: Recommended at error, Strict at error, All at error
This rule checks that extended types have the same kind as their definition, 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 definitions. An # apigenie-lint-disable possible-type-extensions 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.
type User { id: ID! }
extend type User { name: String }
Bad. The linter reports Cannot extend non-object type "User"..
scalar User
extend type User { name: String }
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:
possible-type-extensions: off