This commit adds a sample application to the repository.
This application should not be published as part of the build.
In this application, we're trying to showcase the various features and
use cases with our Spring graphQL integration. We're mixing here data
fetchers backed by datastores or remote hypermedia APIs.
Closes gh-15
This commit adds a very simple graphiQL integration: we're shipping the
project with a sample graphiQL `index.html` page that's relying on CDNs
to display the explorer.
We're also plugging in that resource at the graphQL endpoint location,
responding to GET requests. This is not a problem since for now we're
only considering POST requests to the endpoint for actual queries.
Closes gh-12
The graphQL spec requires that the `variables` object should not be
null. Prior to this commit, the `Map#getOrDefault` call would not
prevent that since it returns the value associated with the key, if
defined, or the default value. In our case the key is defined but the
value is null.
The GraphQL Spring Boot starters aren't actually necessary.
The typical GraphQL usage is really tied to the type of web application
you're building: Spring MVC or WebFlux.
Adding the `spring-graphql-web` dependency to the classpath is a signal
strong enough that we can configure additional endpoints into the web
application.
Closes gh-17
This commit provides an initial instrumentation for metrics support
with micrometer. The graphQL `SimpleInstrumentation` is used to
intercept query execution and collect execution time as well as specific
tags.
The set and names of metrics and tags are temporary and we should refine
this infrastructure.
Closes gh-16
This commit adds the Concourse CI pipeline configuration.
The CI build is hosted on https://ci.spring.io.
As an experimental project, artifacts are published for now using the
org.springframework.experimental groupId.
Closes gh-18
Prior to this commit, the `GraphQLAutoConfiguration` would only consider
the case where the GraphQL schema is read as an SDL from a configured
location.
GraphQL also supports the programmatic creation of the schema and this
case needs to be supported by the auto-configuration.
This commit updates the auto-configuration to disable the schema
creation from the SDL if a `GraphQL.Builder` bean is already contributed
by the application.
Fixes gh-4
- Remove (unused) GraphQLResponseBody
- Collapse servlet and reactive packages and rename handlers to
WebFluxGraphQLHandler and WebMvcGraphQLHandler.
- Minor refactoring and polishing in each handler also removing some
protected methods that overlap in purpose.
- Rename GraphQLRequestBody to RequestInput and make it package private.
This commit removes the controller components and instead moves the web
support to specific auto-configurations.
This commit also adds tests for both web stacks.
This commit adds the relevant dependencies to the web module so as to
move all auto-configurations to a single place. Starter modules will
only ship dependencies as a result.
This commit merges the common, webmvc and webflux modules into a single
web module for supporting GraphQL with all Spring web frameworks.
We're working here with optional dependencies to build the support
for Spring MVC on one side and Spring WebFlux on the other.
Also, this commit updates the starter modules to adopt the official
naming convention. For now, starter modules will host both the
configuration infrastructure and the transitive dependencies to activate
support.
This commit refactors the Gradle build with the following:
* use of the dependency management plugin
* import the Spring Boot BOM for dependency management
* add support for publishing artifacts
