Skip to content
New issue

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

Enable easy customization of GraphQL execution #22

Closed
kaqqao opened this issue Feb 24, 2019 · 0 comments
Closed

Enable easy customization of GraphQL execution #22

kaqqao opened this issue Feb 24, 2019 · 0 comments

Comments

@kaqqao
Copy link
Member

kaqqao commented Feb 24, 2019

In order to customize any of the following:

  • Building ExecutionInput
  • Executing the operation
  • Handling the response

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 app
  • reactive.DefaultGraphQLExecutor - used by the GraphQL controller in a reactive app
  • servlet.websocket.DefaultGraphQLExecutor - used by the WebSocket handler in a servlet-based app

Once WebSockets are supported on the reactive stack, an additional executor will be added.

@kaqqao kaqqao closed this as completed in 50575b4 Feb 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant