add __directive meta field parallel to __type

[yaacovCR]

Use case: inquiring about specific directives such as @defer and @stream

[netlify]

✅ Deploy Preview for graphql-spec-draft ready!

Name	Link
🔨 Latest commit	2196942
🔍 Latest deploy log	https://app.netlify.com/sites/graphql-spec-draft/deploys/66f401a944072500083a7389
😎 Deploy Preview	https://deploy-preview-1114--graphql-spec-draft.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[yaacovCR]

Implemented by graphql/graphql-js#4203

[benjie]

I've not reviewed if these spec changes are sufficient, but I'm supportive of the aim 👍

[yaacovCR]

This was discussed at the November 2024 WG => this small change prompted an interesting discussion about "The Future of Introspection."

To my understanding, @leebyron 's feedback:

Perhaps __type should have always been nested as a type argument under __schema, so that similarly __directive should be nested as directive under __schema.

This general change might unlock general __schema arguments like:

  __schema(includeDeprecated: true) { ... }

that would apply to all nested fields.

As this change is not a "must-have" it will probably be paused to make sure it fits into whatever introspection future is planned. We do not have to actually implement that entire new future to move forward with this small feature change, but we have to make sure that this smaller change aligns with the plan.