Skip to content
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

Jump to bottom

enhance(ResolveFieldValue): note that list items may be async #1066

Merged
merged 3 commits into from
Oct 17, 2024
Merged

enhance(ResolveFieldValue): note that list items may be async #1066

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a5d7731
enhance(ResolveFieldValue): add async collection language
yaacovCR Dec 7, 2023
32b7716
Update spec/Section 6 -- Execution.md
yaacovCR Sep 12, 2024
32053c0
PR feedback
yaacovCR Sep 18, 2024
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
3 changes: 2 additions & 1 deletion spec/Section 6 -- Execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -666,7 +666,8 @@ ResolveFieldValue(objectType, objectValue, fieldName, argumentValues):
Note: It is common for {resolver} to be asynchronous due to relying on reading
an underlying database or networked service to produce a value. This
necessitates the rest of a GraphQL executor to handle an asynchronous execution
flow.
flow. If the field is of a list type, each value in the collection of values
returned by {resolver} may itself be retrieved asynchronously.

### Value Completion

Expand Down
Loading