Update DataFetchingEnvironment docs (#577)

* Update DataFetchingEnvironment docs

* Update other graphql-java v13 links:

Author: smyrick

docs/execution/data-fetching-environment.md

@@ -3,24 +3,43 @@ id: data-fetching-environment
 title: Data Fetching Environment
 ---
 Each resolver has access to a `DataFetchingEnvironment` that provides additional information about the currently executed query including information about what data is requested
-as well as details about current execution state. For more details on the `DataFetchingEnvironment` please refer to [graphql-java documentation](https://www.graphql-java.com/documentation/v13/data-fetching/)
+as well as details about current execution state. For more details on the `DataFetchingEnvironment` please refer to [graphql-java documentation](https://www.graphql-java.com/documentation/v14/data-fetching/)
 
 You can access this info by including the `DataFetchingEnvironment` as one of the arguments to a Kotlin function. This argument will be automatically populated and injected
 during the query execution but will not be included in the schema definition.
 
 ```kotlin
 class Query {
-    fun printEnvironmentInfo(environment: DataFetchingEnvironment): String {
-        // access env data
-    }
+    fun printEnvironmentInfo(parentField: String): MyObject = MyObject()
+}
+
+class MyObject {
+  fun printParentField(childField: String, environment: DataFetchingEnvironment): String {
+    val parentField = environment.executionStepInfo.parent.getArgument("parentField")
+    return "The parentField was $parentField and the childField was $childField"
+  }
 }
 ```
 
 This will produce the following schema
 
 ```graphql
 type Query {
-  printEnvironmentInfo: String!
+  printEnvironmentInfo(parentField: String!): MyObject!
+}
+
+type MyObject {
+  printParentField(childField: String!): String!
+}
+```
+
+Then the following query would return `"The parentField was foo and the childField was bar"`
+
+```graphql
+{
+  printEnvironmentInfo(parentField: "foo") {
+    printParentField(childField: "bar")
+  }
 }
 ```
 

docs/execution/exceptions.md

@@ -4,7 +4,7 @@ title: Exceptions and Partial Data
 ---
 
 Exceptions thrown during execution of a query will result in a GraphQLError that is added to a list of errors of the result. See
-[graphql-java documentation](https://www.graphql-java.com/documentation/v13/execution/) for more details on how to customize your exception handling.
+[graphql-java documentation](https://www.graphql-java.com/documentation/v14/execution/) for more details on how to customize your exception handling.
 
 ### Partial Data
 

docs/execution/fetching-data.md

@@ -6,7 +6,7 @@ title: Fetching Data
 Each field exposed through a GraphQL query has a corresponding resolver (aka data fetcher) associated with it. `graphql-kotlin-schema-generator` generates GraphQL schema
 directly from the source code automatically mapping all the fields either to use
 [FunctionDataFetcher](https://github.com/ExpediaGroup/graphql-kotlin/blob/master/graphql-kotlin-schema-generator/src/main/kotlin/com/expediagroup/graphql/execution/FunctionDataFetcher.kt)
-to resolve underlying functions or a [PropertyDataFetcher](https://www.graphql-java.com/documentation/v13/data-fetching/) to read a value from an underlying Kotlin property.
+to resolve underlying functions or a [PropertyDataFetcher](https://www.graphql-java.com/documentation/v14/data-fetching/) to read a value from an underlying Kotlin property.
 
 While all the fields in a GraphQL query are resolved independently to produce a final result, whether field is backed by a function or a property can have significant
 performance repercussions. For example, given the following schema:

docs/spring-server/spring-beans.md

@@ -23,8 +23,8 @@ can be customized by providing custom beans in your application context. See sec
 |:---------------------------------|:------------|
 | ContextWebFilter                 | Default web filter that populates GraphQL context in the reactor subscriber context. |
 | DataFetcherExceptionHandler      | GraphQL exception handler used from the various execution strategies, defaults to [KotlinDataFetcherExceptionHandler](https://github.com/ExpediaGroup/graphql-kotlin/blob/master/graphql-kotlin-spring-server/src/main/kotlin/com/expediagroup/graphql/spring/exception/KotlinDataFetcherExceptionHandler.kt). |
-| DataLoaderRegistryFactory        | Factory used to create DataLoaderRegistry instance per query execution. See [graphql-java documentation](https://www.graphql-java.com/documentation/v13/batching/) for more details. |
-| GraphQL                          | GraphQL query execution engine generated using `GraphQLSchema` with default async execution strategies. GraphQL engine can be customized by optionally providing a list of [Instrumentation](https://www.graphql-java.com/documentation/v13/instrumentation/) beans (which can be ordered by implementing Spring Ordered interface), [ExecutionIdProvider](https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/ExecutionIdProvider.java) and [PreparsedDocumentProvider](https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/preparsed/PreparsedDocumentProvider.java) in the application context. |
+| DataLoaderRegistryFactory        | Factory used to create DataLoaderRegistry instance per query execution. See [graphql-java documentation](https://www.graphql-java.com/documentation/v14/batching/) for more details. |
+| GraphQL                          | GraphQL query execution engine generated using `GraphQLSchema` with default async execution strategies. GraphQL engine can be customized by optionally providing a list of [Instrumentation](https://www.graphql-java.com/documentation/v14/instrumentation/) beans (which can be ordered by implementing Spring Ordered interface), [ExecutionIdProvider](https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/ExecutionIdProvider.java) and [PreparsedDocumentProvider](https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/preparsed/PreparsedDocumentProvider.java) in the application context. |
 | GraphQLContextFactory            | Factory used by context WebFilter to generate GraphQL context based on the incoming request. GraphQL context can be any object. Defaults to empty [GraphQLContext](https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/GraphQLContext.java). |
 | QueryHandler                     | Handler invoked from GraphQL query route that executes the incoming request, defaults to [SimpleQueryHandler](https://github.com/ExpediaGroup/graphql-kotlin/blob/master/graphql-kotlin-spring-server/src/main/kotlin/com/expediagroup/graphql/spring/execution/QueryHandler.kt). |
 | SubscriptionHandler              | Web socket handler for executing GraphQL subscriptions, defaults to [SimpleSubscriptionHandler](https://github.com/ExpediaGroup/graphql-kotlin/blob/master/graphql-kotlin-spring-server/src/main/kotlin/com/expediagroup/graphql/spring/execution/SubscriptionHandler.kt#L49).<br><br>_Created only if `Subscription` bean is available in the context._ |

docs/writing-schemas/scalars.md

@@ -20,7 +20,7 @@ extended scalar types provided by `graphql-java`.
 | `kotlin.BigDecimal` | `BigDecimal` |
 | `kotlin.Char`       | `Char`       |
 
-> NOTE: Extended GraphQL scalar types provided by `graphql-java` are generated as custom scalar types. When using those custom scalar types your GraphQL clients will have to know how to correctly parse and serialize them. See `graphql-java` [documentation](https://www.graphql-java.com/documentation/v13/scalars/) for more details.
+> NOTE: Extended GraphQL scalar types provided by `graphql-java` are generated as custom scalar types. When using those custom scalar types your GraphQL clients will have to know how to correctly parse and serialize them. See `graphql-java` [documentation](https://www.graphql-java.com/documentation/v14/scalars/) for more details.
 
 ## ID