Problem with @deprecated directive in input fields

[VictorAssunc]

What happened?

After upgrading gqlgen (v0.13.0 -> v0.14.0), when trying to generate models, I got an error related to the @deprecated directive in input fields. I was checking and I'm not sure if it's a gqlgen or gqlparser bug (this second I don't think it's because they updated this directive in a recent commit).

This error did not happen in the previous version (v0.13.0).

What did you expect?

Generate models without problems

Minimal graphql.schema and models to reproduce

input NewUserInput {
  email: String!
  password: String!
  name: String @deprecated(reason: "No longer supported")
}

versions

• gqlgen version? v0.14.0
• go version? go version go1.17 linux/amd64
• dep or go modules? go mod

[bickyeric]

i try to debug this issue, i'm pretty sure this is gqlparser bug on this commit vektah/gqlparser@375e4cf, bug fix already merged but unfortunately not included on gqlparser@v2.2.0 which is used on gqlgen@0.14.0.

i hope gqlparser maintainer can create new release so we can add it into gqlgen v0.15.0 or gqlgen v.0.14.1

[britztopher]

This is definitely keeping me from updating as we use the deprecated directive all over our schema

[BatmanAoD]

Here's the request for a new release in gqlparser: vektah/gqlparser#165

[macnibblet]

That issue has been open for a while, maybe we should fork the gqlparser into 99designs?

[StevenACoffman]

I cut a new release for gqlparser, but it appears not to be that easy as it looks like the very first merge after the v2.2.0 release causes problems in gqlgen generate.

[StevenACoffman]

Sorry this took so long. Should be good now!

[macnibblet]

Thank you sooo much!

[BatmanAoD]

This works! Thank you!

How soon do you expect a new release of gqlgen to be cut?

[imjma]

The error is not happening
But when I tested, there is no deprecated info in the schema or GraohpiQL documentation explorer.

[slightlytyler]

Yep it appears that the codegen supports this now but not the runtime introspection behavior

[StevenACoffman]

PRs welcome!

[carldunham]

fwiw, this is only supported in the working draft gql spec: https://spec.graphql.org/draft/#sec--deprecated. The current spec only allows @deprecated on fields and enums. It may not play nicely with other tooling and/or clients.