Releases: Enigmatis/graphql-java-annotations
Releases · Enigmatis/graphql-java-annotations
v8.0
- graphql-java version updated to v14.0 #245
- The directives mechanism was changed to be applied after the original schema is created (wiring-wise). It's a breaking change because in the past, the wiring mechanism was applied during the schema building using annotations, but now parts of the wiring does happen inside the
GraphQLCodeRegistry
. So you have to use theAnnotationsSchemaCreator
in order to build your schema, or use theGraphQLCodeRegistry
that is composed in theGraphQLAnnotations
processor - Every deprecated method has been deleted (Breaking change)
v7.2.1
v7.2
v7.1
v7.0.1
v7.0
Notice that as part of the breaking change, the usage of graphql-java-annotations is now different: the GraphQLAnnotations
class is not a singleton anymore, and should be constructed.
You also have to obtain the GraphQLCodeRegistry.Builder
from the GraphQLAnnotations
object in order to build your schema properly. You are now able to use the AnnotationsSchemaCreator
in order to build a GraphQLSchema based on your java classes. Read more in our updated readme https://github.com/Enigmatis/graphql-java-annotations
v6.0
v5.4
- Add global strategy to force prettifying all fields/methods #182
MethodDataFetcher
fixes - it now handles cases in which you have to map between source field/method and a method https://github.com/graphql-java/graphql-java-annotations/pull/179/files https://github.com/graphql-java/graphql-java-annotations/pull/175/files
v5.3
- Bugfix: Method data fetcher caused NullPointerException #172
- Added
@Prettify
annotation and cancelled the default behaviour of changing fields names #171 - Remove float support (because it is not supported in graphql-java) #170
- Upgraded to Graphql-Java 8 #169
- Allow sending arguments in data fetcher annotation #167
- Bugfix in union #165
- Allow custom paging implementation #163
- #161
- Added support for arrays #159