Merge pull request #10 from graphql-java-kickstart/add-missing-option-descriptions

Add missing option descriptions

Author: vojtapol

content/tools/getting-started/index.md

@@ -9,12 +9,12 @@ menu:
  url: /tools/getting-started/
 ---
 
-A working [Java Spring-Boot application](https://github.com/graphql-java-kickstart/graphql-java-tools/tree/master/example) is provided,
+A working [Java Spring-Boot application](https://github.com/graphql-java-kickstart/samples/tree/master/tools-hello-world) is provided,
 based off the [Star Wars API](https://github.com/graphql-java/graphql-java/blob/master/src/test/groovy/graphql/StarWarsSchema.java) tests
 and [test data](https://github.com/graphql-java/graphql-java/blob/master/src/test/groovy/graphql/StarWarsData.groovy).
 If you're using Spring Boot, check out the [graphql-spring-boot-starter](https://github.com/graphql-java-kickstart/graphql-spring-boot)!
 
-A working [Kotlin example](https://github.com/graphql-java-kickstart/graphql-java-tools/blob/master/src/test/kotlin/com/coxautodev/graphql/tools/EndToEndSpec.kt) can be found in the tests.
+A working [Kotlin example](https://github.com/graphql-java-kickstart/graphql-java-tools/blob/master/src/test/kotlin/graphql/kickstart/tools/EndToEndSpecHelper.kt) can be found in the tests.
 
 ## Quick start
 
@@ -50,7 +50,7 @@ Add the `graphql-java-tools` dependency:
 ## Using the latest development build
 
 Snapshot versions of the current `master` branch are available on JFrog. Check the next snapshot version on
-[Github](https://github.com/graphql-java-kickstart/graphql-java-tools/blob/master/gradle.properties)
+[Github](https://github.com/graphql-java-kickstart/graphql-java-tools/blob/master/pom.xml#L7)
 
 ### Build with Gradle
 

content/tools/schema-parser-options/index.md

@@ -14,11 +14,14 @@ Use `SchemaParserOptions.newBuilder()` to build an options object to pass to the
 
 Options:
 
+* `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.
 * `genericWrappers`: Allows defining your own generic classes that should be unwrapped when matching Java types to GraphQL types. You must supply the class and 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`.
 
 * `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`.
 * `allowUnimplementedResolvers`: Defaults to `false`. Allows a schema to be created even if not all GraphQL fields have resolvers. Intended only for development, it will log a warning to remind you to turn it off for production. Any unimplemented resolvers will throw errors when queried.
-* `objectMapperConfigurer`: Exposes the Jackson `ObjectMapper` that handles marshalling arguments in method resolvers. Every method resolver gets its own mapper, and the configurer can configure it differently based on the GraphQL field definition.
+* `missingResolverDataFetcher`: Allows you to provide custom behavior for missing GraphQL fields.
+* `inputArgumentOptionalDetectOmission`: Defaults to `false`. By default, the parser will treat omitted or null method input arguments as `Optional.empty` in resolvers. If you prefer, you can disable this behavior.
+* `objectMapperConfigurer` / `objectMapperProvider`: Exposes the Jackson `ObjectMapper` that handles marshalling arguments in method resolvers. Every method resolver gets its own mapper, and the configurer can configure it differently based on the GraphQL field definition.
 * `preferGraphQLResolver`: In cases where you have a Resolver class and legacy class that conflict on type arguments, use the Resolver class instead of throwing an error.
  Specifically this situation can occur when you have a graphql schema type `Foo` with a `bars` property and classes:
  ```java
@@ -38,3 +41,13 @@ Options:
  ```
  You will now have the code find two different return types for getBars() and application will not start with the error ```Caused by: com.coxautodev.graphql.tools.SchemaClassScannerError: Two different classes used for type```
  If this property is true it will ignore the legacy version.
+* `addProxyHandler`: If your runtime resolver classes are auto-generated proxies of some kind you can provide a handler to help the parser find the real resolvers behind them. Four proxy handlers are provided by default for these libraries:
+ * Javassist
+ * Guice
+ * Spring AOP
+ * Weld
+* `introspectionEnabled`: Defaults to `true`. When set to `false` this option will disable schema introspection via `NO_INTROSPECTION_FIELD_VISIBILITY`. See [Field Visibility](https://www.graphql-java.com/documentation/master/fieldvisibility/).
+* `fieldVisibility`: Provide a graphql field visibility implementation. This option overrides `introspectionEnabled` when used. See [Field Visibility](https://www.graphql-java.com/documentation/master/fieldvisibility/).
+* `coroutineContext` / `coroutineContextProvider`: Provide a kotlin coroutine context to be used with suspend functions of resolvers.
+* `typeDefinitionFactory`: See [Type Definition Factory]({{< relref "/tools/type-definition-factory/index.md" >}}).
+* `includeUnusedTypes`: Defaults to `false`. By default, the parser will ignore unused type definitions in the schema. Enable this option to include them regardless.

content/tools/type-definition-factory/index.md

@@ -9,11 +9,11 @@ menu:
  url: /tools/type-definition-factory/
 ---
 
-The **Type Definition Factory** has been added with to be able to dynamically
+The **Type Definition Factory** has been added to allow to dynamically
 add type definitions to the schema instead of having to define them manually
 in the SDL. There are a couple of use cases where the types that have to be defined
 are very much alike and only certain parts are different. For example the
-connection and edge types used by [Relay]({{< relref "/tools/relay/index.md" >}}). Since generics isn't supported in
+connection and edge types used by [Relay]({{< relref "/tools/relay/index.md" >}}). Since generics aren't supported in
 the definition language this type definition factory has been added.
 
 ## Basic usage