Incorporate meta-fields into ExecuteCollectedFields
At a glance​
- Identifier: #1177
- Stage: RFC0: Strawman
- Champion: @benjie
- PR: Incorporate meta-fields into ExecuteCollectedFields
Timeline​
- Spec PR created on 2025-07-03 by benjie
- Commit pushed: Incorporate meta-fields into ExecuteCollectedFields on 2025-07-03 by @benjie
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 theExecuteField()
andExecuteCollectedFields()
algorithms in the spec - specifically,executeField()
may returnundefined
, resulting inexecuteFields()
not adding the entry to the result object, whereas this conditional addition is handled inExecuteCollectedFields()
in the spec and we cannot/should not differentiate betweennull
andundefined
in this way.)