Missing support for deprecated field arguments & input type fields

[CodingContraption]

We ran into a problem recently with graphql-protect, used to protect an apollo-router GraphQL API.

The latest apollo-router supports a draft version of the spec, that adds support for deprecated input values: graphql/graphql-spec#805

Currently gqlparser support is still at the 2018 spec, resulting in errors when a client requests introspection fields like isDeprecated and deprecationReason on the __InputValue.

To fix this the prelude.graphql should be updated to include the draft introspection schema. Next to that, there are a few updated validation rules that need adoption as well.

[CodingContraption]

I've created PR #342 to try and update to the latest draft spec. Because the draft is a living document, I've opted to take the graphql-js:16.10.0 release spec support as a baseline.

[StevenACoffman]

Thanks! Can you describe what your process was to update the prelude.graphql? I have been doing it fairly manually and that makes keeping it current a huge problem, but I've got to think that I can leverage either the spec or the graphql-js reference implementation better for that step of the process. Any insight into what you did (as opposed to my own "feels right to me" process) would be helpful.

The GraphQL committee (and it's spec) doesn't do as good of a job as more formal standards bodies like IETF in frequently publishing unambiguous spec changes, and communicating the status of drafts. The graphql-js reference implementation appears to be more authoritative than the spec document.

[CodingContraption]

First of all, thanks for the quick review & merge!

To be honest this is the first time I had a look at this, so it ended up as a manual process to me as well. One part of it was copying the draft spec spec for introspection here: https://spec.graphql.org/draft/#sec-Schema-Introspection.Schema-Introspection-Schema

After that, I did notice that the oneOf directive was introduced, which I manually added as well.

One thing I did notice is that the graphql-js/src/utilities/__tests__/printSchema-test.ts file appears to test printing a full introspection schema, which is effectively the same to the prelude.graphql save for some changes to docs & missing the builtin scalars. Perhaps that could be something to leverage?

[CodingContraption]

I've tinkered a bit with the export.js script, and I did manage to generate a prelude.graphql file using graphql-js, but I did still have to append hardcoded text for the builtin scalars & the @defer directive to achieve parity with the current prelude.graphql file.

CodingContraption@715dc9b