We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In order to customize any of the following:
ExecutionInput
it is currently necessary to override the whole controller and/or WebSocket handler.
To facilitate easier customization, all of these concerns are now delegated to GraphQLExecutor implementation that can easily be swapped by the user.
GraphQLExecutor
Right now, 3 built-in implementations exist (with at least 1 more to come):
servlet.DefaultGraphQLExecutor
reactive.DefaultGraphQLExecutor
servlet.websocket.DefaultGraphQLExecutor
Once WebSockets are supported on the reactive stack, an additional executor will be added.
The text was updated successfully, but these errors were encountered:
50575b4
No branches or pull requests
In order to customize any of the following:
ExecutionInput
it is currently necessary to override the whole controller and/or WebSocket handler.
To facilitate easier customization, all of these concerns are now delegated to
GraphQLExecutor
implementation that can easily be swapped by the user.Right now, 3 built-in implementations exist (with at least 1 more to come):
servlet.DefaultGraphQLExecutor
- used by the GraphQL controller in a servlet-based appreactive.DefaultGraphQLExecutor
- used by the GraphQL controller in a reactive appservlet.websocket.DefaultGraphQLExecutor
- used by the WebSocket handler in a servlet-based appOnce WebSockets are supported on the reactive stack, an additional executor will be added.
The text was updated successfully, but these errors were encountered: