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
|`isBatchResource`| Is this a batch resource? (Can you pass it a list of keys and get a list of results back?) |
119
-
|`docsLink`| The URLfor the documentation of the resource. Usefulfor others to verify information is correct, and may be used in stack traces. |
120
-
|`batchKey`| The argument to the resource that represents the list of entities we want to fetch. (e.g. 'user_ids') |
121
-
|`newKey`| The argument we'll replace the batchKey with - should be a singular version of the `batchKey` (e.g. 'user_id') |
122
-
| `reorderResultsByKey` | (Optional) If the resource itself does not guarantee ordering, use this to specify which key in the response objects corresponds to an element in `batchKey`. Transforms and re-order the response to the same order as requested from the DataLoaders. |
123
-
| `nestedPath` | (Optional) If the resource returns the list of results in a nested path (e.g. `{ results: [ 1, 2, 3 ] }`), this tells the DataLoader where in the response to find the results. (e.g. 'results'). |
124
-
| `commaSeparatedBatchKey` | (Optional) Set to true if the interface of the resource takes the batch key as a comma separated list (rather than an array of IDs, as is more common). Default: false |
125
-
| `isResponseDictionary` | (Optional) Set to true if the batch resource returns the results as a dictionary with key mapped to values (instead of a list of items). If this option is supplied `reorderResultsByKey` should not be. Default: false |
|`isBatchResource`| Is this a batch resource? (Can you pass it a list of keys and get a list of results back?) |
120
+
|`docsLink`| The URLfor the documentation of the resource. Usefulfor others to verify information is correct, and may be used in stack traces. |
121
+
|`batchKey`| The argument to the resource that represents the list of entities we want to fetch. (e.g. 'user_ids') |
122
+
|`newKey`| The argument we'll replace the batchKey with - should be a singular version of the `batchKey` (e.g. 'user_id') |
123
+
| `reorderResultsByKey` | (Optional) If the resource itself does not guarantee ordering, use this to specify which key in the response objects corresponds to an element in `batchKey`. Transforms and re-order the response to the same order as requested from the DataLoaders. |
124
+
| `nestedPath` | (Optional) If the resource returns the list of results in a nested path (e.g. `{ results: [ 1, 2, 3 ] }`), this tells the DataLoader where in the response to find the results. (e.g. 'results'). |
125
+
| `commaSeparatedBatchKey` | (Optional) Set to true if the interface of the resource takes the batch key as a comma separated list (rather than an array of IDs, as is more common). Default: false |
126
+
| `isResponseDictionary` | (Optional) Set to true if the batch resource returns the results as a dictionary with key mapped to values (instead of a list of items). If this option is supplied `reorderResultsByKey` should not be. Default: false |
127
+
| `isBatchKeyASet` | (Optional) Set to true if the interface of the resource takes the batch key as a set (rather than an array). For example, when using a generated clientlib based on swagger where `uniqueItems: true` is set for the batchKey parameter. Default: false. |
0 commit comments