Skip to content

Commit 1e48b21

Browse files
committed
Incorporate meta-fields into ExecuteCollectedFields
1 parent b1a23de commit 1e48b21

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

spec/Section 6 -- Execution.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -581,9 +581,14 @@ variableValues):
581581
- For each {responseName} and {fields} in {collectedFieldsMap}:
582582
- Let {fieldName} be the name of the first entry in {fields}. Note: This value
583583
is unaffected if an alias is used.
584-
- Let {fieldType} be the return type defined for the field {fieldName} of
585-
{objectType}.
586-
- If {fieldType} is defined:
584+
- If {fieldName} is a meta-field as defined in the Introspection section:
585+
- Let {responseValue} be the result of resolving that meta-field as per the
586+
rules of the [Introspection](#sec-Introspection) section.
587+
- Set {responseValue} as the value for {responseName} in {resultMap}.
588+
- Otherwise, if a field named {fieldName} is defined on {objectType}:
589+
- Let {fieldType} be the return type defined for the field {fieldName} of
590+
{objectType}.
591+
- Assert: {fieldType} must exist.
587592
- Let {responseValue} be {ExecuteField(objectType, objectValue, fieldType,
588593
fields, variableValues)}.
589594
- Set {responseValue} as the value for {responseName} in {resultMap}.

0 commit comments

Comments
 (0)