You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-17Lines changed: 20 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ It works as follows:
9
9
* Each of many concurrently executing graphql resolver functions call Load() on the Loader object with different keys. Let's say K1, K2, K3
10
10
* Each call to Load() with a new key is delayed slightly (a few milliseconds) so that the Loader can load them together.
11
11
* The customizable fetch function of the loader takes a list of keys and loads data for all of them in a single batched request to the data storage layer. It might send `[K1,K2,K3]` and get back `[V1,V2,V3]`.
12
-
* The Loader takes case of sending the right resight to the right caller and the result is cached for the duration of the graphql request.
12
+
* The Loader takes case of sending the right result to the right caller and the result is cached for the duration of the graphql request.
13
13
14
14
Usage:
15
15
@@ -31,7 +31,8 @@ import (
31
31
)
32
32
33
33
// fetchFn is shown as a function here, but it might work better as a method
0 commit comments