Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow deprecating input values #1891

Closed
jhalborg opened this issue Sep 25, 2023 · 2 comments
Closed

Allow deprecating input values #1891

jhalborg opened this issue Sep 25, 2023 · 2 comments

Comments

@jhalborg
Copy link

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

@dimaMachina
Copy link
Collaborator

what version of graphql are you using?

@dimaMachina
Copy link
Collaborator

Closing due silence, feel free to reply and I’ll reopen

@dimaMachina dimaMachina closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants