-
Notifications
You must be signed in to change notification settings - Fork 317
Add client-side interception on GraphQlClient #332
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
Comments
Closed
rstoyanchev
added a commit
that referenced
this issue
Mar 21, 2022
rstoyanchev
added a commit
that referenced
this issue
Mar 21, 2022
Rename the implementation classes Request[Input|Output] accordingly to match the interfaces, and move them into the support package. Create AbstractGraphQlResponse in the support package that pre-implements response field access. This leaves mainly contracts in the top-level package. See gh-332
rstoyanchev
added a commit
that referenced
this issue
Mar 21, 2022
rstoyanchev
added a commit
that referenced
this issue
Mar 21, 2022
Rename GraphQlService to ExecutionGraphQlService following the renaming of the request and response to ExecutionGraphQl[Request|Response]. See gh-332
rstoyanchev
added a commit
that referenced
this issue
Mar 21, 2022
bclozel
added a commit
to spring-projects/spring-boot
that referenced
this issue
Mar 21, 2022
This commit adapts to the latest Spring GraphQL changes, renaming `GraphQlService` to `ExecutionGraphQlService` as well as the `WebInterceptor` contract to `WebGraphQlHandlerInterceptor`. See spring-projects/spring-graphql#332
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to the
WebInterceptor
chain on the server side but for use withGraphQlClient
. This would also include a WebSocket specific interceptor for WebSocket specific needs (connection_init
andconnection_ack
payload, disconnects, etc).The text was updated successfully, but these errors were encountered: