@@ -656,12 +656,6 @@ As an example, this might accept the {objectType} `Person`, the {field}
656
656
{"soulMate"}, and the {objectValue} representing John Lennon. It would be
657
657
expected to yield the value representing Yoko Ono.
658
658
659
- List values are resolved similarly. For example, {ResolveFieldValue} might also
660
- accept the {objectType} ` MusicBand ` , the {field} {"members"}, and the
661
- {objectValue} representing the Beatles. It would be expected to yield a
662
- collection of values representing John Lennon, Paul McCartney, Ringo Starr and
663
- George Harrison.
664
-
665
659
ResolveFieldValue(objectType, objectValue, fieldName, argumentValues):
666
660
667
661
- Let {resolver} be the internal function provided by {objectType} for
@@ -672,9 +666,8 @@ ResolveFieldValue(objectType, objectValue, fieldName, argumentValues):
672
666
Note: It is common for {resolver} to be asynchronous due to relying on reading
673
667
an underlying database or networked service to produce a value. This
674
668
necessitates the rest of a GraphQL executor to handle an asynchronous execution
675
- flow. In addition, for fields that have a return type that is a List type, each
676
- value in a collection of values returned by {resolver} may be retrieved
677
- asynchronously.
669
+ flow. If the field is of a list type, each value in the collection of values
670
+ returned by {resolver} may itself be retrieved asynchronously.
678
671
679
672
### Value Completion
680
673
0 commit comments