Incorporate meta-fields into ExecuteCollectedFields

[benjie]

GraphQL.js uses a getFieldDef() helper:

https://github.com/graphql/graphql-js/blob/9032db1e4e55052bead6936359ecc5592c817f64/src/execution/execute.ts#L1047-L1079

called from executeField() to get the field definition to execute; returning meta-field definitions as appropriate.

This spec change reflects this existing behavior as best we can.

(Technically GraphQL.js' executeField() function overlaps responsibilities between the ExecuteField() and ExecuteCollectedFields() algorithms in the spec - specifically, executeField() may return undefined, resulting in executeFields() not adding the entry to the result object, whereas this conditional addition is handled in ExecuteCollectedFields() in the spec and we cannot/should not differentiate between null and undefined in this way.)

[netlify]

✅ Deploy Preview for graphql-spec-draft ready!

Name	Link
🔨 Latest commit	4b7c111
🔍 Latest deploy log	https://app.netlify.com/projects/graphql-spec-draft/deploys/6867d29d68a7bb0008666675
😎 Deploy Preview	https://deploy-preview-1177--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 project configuration.

[benjie]

@leebyron I think this matches what you had in mind? (Leaving the resolvers of the introspection system to be the behaviour of those defined within that section of the spec.)