At a glance
- Identifier: #1177
- Stage: RFC 1 / Proposal
- Champion: @benjie
- Latest activity: 4 commits pushed on 2025-07-04
- Spec PR: https://github.com/graphql/graphql-spec/pull/1177
Spec PR description
GraphQL.js uses a getFieldDef() helper:
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.)
Timeline
- 4 commits pushed on 2025-07-04:
- benjie committed "Introduce ResolveMetaFieldValue algorithm"
- benjie committed "Refactor to add assertion"
- benjie committed "This should require less refactoring when we add future meta-fields"
- benjie committed "Could be an introspection type"
- Spec PR created on 2025-07-03 by benjie
- Commit pushed on 2025-07-03 by benjie: Incorporate meta-fields into ExecuteCollectedFields
- Added to WG agenda on 2025-07-03