6.1.0

Minor changes

• Validation directives on nested Input fields example #385
• Upgrade to graphql-java 14.1

Breaking changes

• If parameter is of type Optional its value is now set to Optional.empty() for both omitted and null argument. To get the old behavior back set inputArgumentOptionalDetectOmission to true.
• Support for the deprecated @Batched annotation has been removed.

6.0.2

Use copy of schema directive helper classes from graphql-java instead of relying on reflection.

6.0.1

• Removed Guava dependency
• Upgraded dependencies of kotlin and jackson
• List of IDs not resolved correctly #367

6.0.0

Thanks to the contributors the following issues have been fixed in this release:

• Upgrade graphql-java to version 14
• Renamed base package to graphql.kickstart.tools
• Treat non-nullable scalars as scalars #341
• Treat array of non-null scalars as scalars #358
• Add the TrivialDataFetcher interface to MethodFieldResolver so that it can be excluded from tracing #337
• Ignore proxies when scanning for field resolvers #348
• Make coroutine scope configurable via context #350
• Add compile check for dependency convergence #352
• Changed default CoroutineScope to not use GlobalScope to avoid potential cancellation issues and other pitfalls #359
• Fix unwrapGenericType to properly find generic type in arguments Map #361
• Move DirectiveBehavior out of graphql.schema.idl package #364

5.6.1

Thanks to the contributors the following issues have been fixed in this release:

• Upgrade graphql-java to version 13
• Warning log: Schema type was defined but can never be accessed, and can be safely deleted: PageInfo #215
• Nullable boolean in input with default value throws CoercingSerializeException #251
• Default values for enum fields on input types not set correctly #257
• Utils throws IllegalAccessException in JDK 9 or higher #265
• GraphQLCodeRegistry.Builder is null in custom SchemaDirectiveWirings #268
• Possible type leaking when serializing java -> graphql #276
• SchemaParser#createInputObject issue creating directives #280

5.6.0

Upgraded to graphql-java 12.0

5.5.2

Enhancements

• Allow configuration of CoroutineContextProvider so that context can be created per request instead of just at startup

Bugfixes

• Add arguments in correct order when creating building Object

5.4.1

Enhancements

• #166 Support for directives on ENUM_VALUE
• #213 Accept List in SchemaParserBuilder.scalars

Bugfixes

• #209 Unable to match type definition
• #210 RelayConnectionFactory generates nullable connection types
• #188 Cannot find field from parent interface
• #183 Unable to find generic type of class... for an interface

5.4.0

Features

Graphql-java 11.0

Upgraded graphql-java to 11.0. See their release notes fur further details.

Type Definition Factory

Added the type definition factory to make it possible to dynamically add type definitions after the SDL has been parsed. This is used to automatically generate Relay connection type definitions. See https://www.graphql-java-kickstart.com/tools/type-definition-factory/ for more details.

Automatic generation of Relay Type Definitions

Relay Type Definitions can now be automatically generated using the @connection directive. See https://www.graphql-java-kickstart.com/tools/relay/ for more details and basic usage.

Directives

Support for directives has been included now. See https://www.graphql-java-kickstart.com/tools/directives/ for more details and basic usage.

Other features

#104 Coroutine support

5.3.5

Support Java 11

Upgraded commons-lang3 to version 3.8.1 to support Java 11.