I am pleased to announce that the third Spring for GraphQL 2.0 Milestone release is now available.

Nullability support in schema mapping inspection

Our Schema Mapping Inspection feature got a recent upgrade thanks to our work on Null-safety in Spring projects.

If your application is written in Kotlin, or is using Null-safety annotations, further inspections will be performed. The GraphQL schema can declare nullable types (Book) and non-nullable types (Book!). We can ensure that both the schema and the application are in sync when it comes to nullability information.

• For schema fields, we can check that the relevant Class properties and DataFetcher return types with the same nullability.
• For field arguments, we can ensure that DataFetcher parameters have the same nullability

With this feature, we are finally connecting the nullability information from the schema to application types.

Aligning with the cursor connection support

We fixed the generation process for the *Connection types in your schema. We are now better aligning with the official specification by creating a nullable collection edges: [*Edge] instead of the previously non-nullable one.

This is a small but important change that will be reflected in your application schema.

Request cancellation support

Spring for GraphQL already supported request cancellation, effectively preventing further data fetching if the main request is cancelled by the client. With GraphQL Java 25, we have now switched to the new official implementation of that feature by the project team.

What's next?

We have compiled all release notes on our wiki. Our first and only release candidate is scheduled next month. We have completed most of our goals for this generation, but it's still time to send feedback our way!

2.0.0-M3 is now available from https://repo.spring.io and Maven Central.

How can you help?

If you have general questions, please ask on stackoverflow.com using the spring-graphql tag.

Project Page | GitHub | Issues | Documentation | Stack Overflow