input-output-types

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

This rule checks that arguments and input fields have input types, and fields have output types, 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 input-output-types 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 Query { users(filter: UserFilter): [User] }
input UserFilter { name: String }
type User { id: ID! }

Bad. The linter reports The type of Query.users(filter:) must be Input Type but got: User..

type Query { users(filter: User): [User] }
type User { id: 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:
        input-output-types: off

Further reading

Last updated on View as Markdown
Was this helpful?