Skip to content

Allow deprecating input values #1891

Closed as not planned
Closed as not planned
@jhalborg

Description

@jhalborg

Describe the bug

Using @deprecated on an input field throws the following error in this tool:

error Parsing error: [graphql-eslint] Error while loading schema: Directive "@deprecated" may not be used on ARGUMENT_DEFINITION

The spec has merged the ability to deprecate input values in this PR

To Reproduce Steps to reproduce the behavior:

Add a @deprecated notice on an input field, i.e.

type Mutation {
  myMutation(firstParam: String @deprecated(reason: "Value taken from token instead"), secondParam: String!): String!

Expected behavior
A normal lint warning on the deprecated field

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions