16aa33a2fb
Prior to this commit, the `GraphQlHttpHandler` implementations for MVC and WebFlux would support the HTTP transport protocol for servers. They would align with the well-known GraphQL behavior, using HTTP as a transport and always using HTTP 200 OK as response status. The new GraphQL over HTTP specification changes that, and requires servers to respond with HTTP 4xx/5xx statuses when an error occurs before the GraphQL request execution: for example, if the JSON document cannot be parsed, or the GraphQL document is invalid. This commit introduces a new "standard mode" option on HTTP transports to follow this new requirement. Because this is a breaking change for GraphQL clients, this mode is opt-in only for now. See gh-1117
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.