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: content/tools/schema-parser-options/index.md
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,14 @@ Use `SchemaParserOptions.newBuilder()` to build an options object to pass to the
14
14
15
15
Options:
16
16
17
-
*`contextClass`: If you use a context object to execute your queries, let the parser know about it so that it can add it to data fetchers as an argument.
17
+
*`contextClass`: If you use a custom context object to execute your queries, let the parser know about it so that it can add it to data fetchers as an argument.
18
+
Make sure to also provide your context instance to the execution input:
19
+
```java
20
+
var executionInput =ExecutionInput.newExecutionInput()
* `genericWrappers`:Allows defining your own generic classes that should be unwrapped when matching Java types to GraphQL types. You must supply the classand the index (zero-indexed) of the wrapped generic type. For example: If you want to unwrap type argument `T` of `Future<T>`, you must pass `Future.class` and `0`.
19
26
20
27
* `useDefaultGenericWrappers`: Defaults to `true`. Tells the parser whether or not to add it's own list of well-known generic wrappers, such as `Future` and `CompletableFuture`.
0 commit comments