Handle deprecation of inputs

[fotoetienne]

Deprecation of input values has now been merged into the GraphQL spec. This includes a modification to the introspection query.

Without includeDeprecated = true on inputFields in the introspection query, an error occurs on any input objects that have all fields deprecated:
Error: Invalid schema from introspection: Input Object type <typename> must define one or more fields.

GraphiQL now has a flag that determines whether the introspection query should include includeDeprecated = true on inputFields, since only compatible graphs will know about this argument. Sandbox/explorer could do something similar or somehow autodetect whether the graph supports deprecation of input fields.

You just need to set the inputValueDeprecation arg in the graphql-js getIntrospectionQuery function.

[fotoetienne]

Digging in a bit, I see inputValueDeprecation included in introspectionOptions in src/app/graph/explorerPage/hooks/useExplorerState/useSchema/useSchemaFromEndpointIntrospection/useSchemaFromEndpointIntrospection.ts so maybe this just needs to be exposed or documented.

We are using the embedded sandbox in apollo-router and currently seeing the error described above.

[fotoetienne]

After more inspection, it seems that the introspection query does include deprecated on inputs. Nevertheless, there is an error in the console for an input type that has all fields deprecated

[mayakoneval]

Hey! Apologies for the late reply here.

This should be checking the introspection response to see if your __Directive type has includeDeprecated as an arg, and passing includeDeprecated to the introspection options when generating the query already.

I tested on a schema with a deprecated input field and am seeing it work alright: https://codesandbox.io/p/sandbox/as4-integration-testing-e90bft?file=%2Fsrc%2Fserver.ts%3A11%2C1-13%2C4

Would you be able to validate for me the version of graphql js you are using? 🙏🏻

[mayakoneval]

closing as we have not heard back