Skip to content

Edit: fieldType may not be defined, but will never be null #433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leebyron merged 1 commit into from
Apr 30, 2018
Merged

Edit: fieldType may not be defined, but will never be null #433

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions spec/Section 6 -- Execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,10 +319,9 @@ ExecuteSelectionSet(selectionSet, objectType, objectValue, variableValues):
* Let {fieldName} be the name of the first entry in {fields}.
Note: This value is unaffected if an alias is used.
* Let {fieldType} be the return type defined for the field {fieldName} of {objectType}.
* If {fieldType} is {null}:
* Continue to the next iteration of {groupedFieldSet}.
* Let {responseValue} be {ExecuteField(objectType, objectValue, fields, fieldType, variableValues)}.
* Set {responseValue} as the value for {responseKey} in {resultMap}.
* If {fieldType} is defined:
* Let {responseValue} be {ExecuteField(objectType, objectValue, fields, fieldType, variableValues)}.
* Set {responseValue} as the value for {responseKey} in {resultMap}.
* Return {resultMap}.

Note: {resultMap} is ordered by which fields appear first in the query. This
Expand Down