Field args marked as `@deprecated` are lost when getting schema over HTTP

[mikew]

Which packages are impacted by your issue?

No response

Describe the bug

Given a schema like

type Query {
    example(arg: ID @deprecated): ID
}

type Foo {
    example(arg: ID @deprecated): ID
}

The args for the various fields that are marked as @deprecated are lost in all files generated by graphql-code-generator.

schema-ast produces:

type Foo {
  example: ID
}

type Query {
  example: ID
}

introspection produces:

      {
        "kind": "OBJECT",
        "name": "Foo",
        "description": null,
        "fields": [
          {
            "name": "example",
            "description": null,
            "args": [],
            "type": {
              "kind": "SCALAR",
              "name": "ID",
              "ofType": null
            },
            "isDeprecated": false,
            "deprecationReason": null
          }
        ],
        "inputFields": null,
        "interfaces": [],
        "enumValues": null,
        "possibleTypes": null
      },
      {
        "kind": "OBJECT",
        "name": "Query",
        "description": null,
        "fields": [
          {
            "name": "example",
            "description": null,
            "args": [],
            "type": {
              "kind": "SCALAR",
              "name": "ID",
              "ofType": null
            },
            "isDeprecated": false,
            "deprecationReason": null
          }
        ],
        "inputFields": null,
        "interfaces": [],
        "enumValues": null,
        "possibleTypes": null
      },

typescript generates

export type Foo = {
  __typename?: 'Foo';
  example?: Maybe<Scalars['ID']['output']>;
};

export type Query = {
  __typename?: 'Query';
  example?: Maybe<Scalars['ID']['output']>;
};

Your Example Website or App

https://stackblitz.com/edit/github-t8cgka

Steps to Reproduce the Bug or Issue

Visit the stackblitz reproduction and wait a few seconds for the server to start and graphql-code-generator to run

Expected behavior

I expect the args marked as @deprecated to be included

Screenshots or Videos

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• NodeJS: [e.g. 18.5.0]
• graphql version: [e.g. 16.3.0]
• @graphql-codegen/* version(s): [e.g. 2.6.2]

Codegen Config File

No response

Additional context

No response

[kkieninger]

In case it is helpful, I can confirm I am experiencing the same issue with the latest versions of the following:

"@graphql-codegen/cli": "^5.0.0",
"@graphql-codegen/schema-ast": "^4.0.0",
"@graphql-codegen/near-operation-file-preset": "^3.0.0",
"@graphql-codegen/typescript": "^4.0.1",
"@graphql-codegen/typescript-operations": "^4.0.1"

[mikew]

We worked around this by using a custom loader. Maybe there's an easier way, because the fix seems to just be what options are passed to getIntrospectionQuery

const fetch = require('cross-fetch')
const { getIntrospectionQuery, buildClientSchema } = require('graphql')

module.exports = async () => {
  const introspectionQuery = getIntrospectionQuery({
    descriptions: true,
    directiveIsRepeatable: true,
    inputValueDeprecation: true,
    schemaDescription: true,
    specifiedByUrl: true,
  })

  const response = await fetch('https://example.com', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ query: introspectionQuery })
  })

  const data = await response.json()

  return buildClientSchema(data.data)
}

[oceandrama]

Can confirm this issue with

"@graphql-codegen/add": "5.0.0",
"@graphql-codegen/cli": "5.0.0",
"@graphql-codegen/fragment-matcher": "5.0.0",
"@graphql-codegen/near-operation-file-preset": "2.5.0",
"@graphql-codegen/schema-ast": "4.0.0",
"@graphql-codegen/typescript": "4.0.1",
"@graphql-codegen/typescript-operations": "4.0.1",
"@graphql-codegen/typescript-react-apollo": "3.3.7",

[MeetM15]

We are facing the same issue and it is affecting us severely , can we get a fix for this soon.
These are the package versions we are using for reference.

"@graphql-codegen/add": "^5.0.0",

"@graphql-codegen/cli": "5.0.0",

"@graphql-codegen/import-types-preset": "^3.0.0",

"@graphql-codegen/typed-document-node": "^5.0.1",

"@graphql-codegen/typescript": "4.0.1",

"@graphql-codegen/typescript-operations": "^4.0.1"

[Stephen2]

same here:

        "@graphql-codegen/cli": "^5.0.2",
        "@graphql-codegen/client-preset": "^4.2.5",

[AaronMoat]

While undocumented, this seems to work:

generates:
  ./src/blah:
     schema: some-url
     ....

config:
  ...
  inputValueDeprecation: true

[Bryceacampbell]

While undocumented, this seems to work:

generates:
  ./src/blah:
     schema: some-url
     ....

config:
  ...
  inputValueDeprecation: true

I ran into the same issue and this fixed it. Thank you

[mikew]

@AaronMoat That's a great tip! I figured it must be possible without any custom code.

[ya2s]

@AaronMoat @mikew
This workaround works for codegen.js, but not when leveraging graphql config

[itdhsc]

We faced a similar issue in our project. After implementing the workaround, we can confirm that it effectively resolved the problem.