acb182844b
As of gh-1149, CANCEL signals are propagated from the transport request up to reactive `DataFetcher`s. This efficiently cancels processing and avoids spending resources when execution results won't be sent to the client. Prior to this commit, this would have no effect on non-reactive `DataFetcher`s because they would still be executed. While we cannot consistently cancel ongoing blocking operations, we can avoid further processing and other `DataFetcher`s from being called by returning an error result instead of the original result. This commit updates the `ContextDataFetcherDecorator` to detect if the request has been cancelled and return early a data fetcher result with a `AbortExecutionException` error instead of the original result. Closes gh-1153
Spring for GraphQL 
GraphQL support for Spring applications with GraphQL Java.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.
Contributing
All commits must include a Signed-off-by trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin. For additional details, please refer to the blog post Hello DCO, Goodbye CLA: Simplifying Contributions to Spring.
Documentation
This project has reference documentation (published and source), an API reference. There are samples in the 1.0.x branch that will be moved out into a separate repository.
Stay in Touch
Follow @SpringCentral.
Getting Support
Check out the Spring GraphQL tags on Stack Overflow. Commercial support is available too.
License
This project is released under version 2.0 of the Apache License.