You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Is your feature request related to a problem? Please describe.
In our app, it is normal and expected to have non-login users accessing the pages, where we will return as auth error for some queries. It is annoying to always log the stacktrace for such cases.
However, it is not easy to embed it with kickstart library right now.
Describe the solution you'd like
Expecting a non-required bean for DataFetcherExceptionHandler, so that it could be passed into the below places when building Execution strategy:
Is your feature request related to a problem? Please describe.
In our app, it is normal and expected to have non-login users accessing the pages, where we will return as auth error for some queries. It is annoying to always log the stacktrace for such cases.
Graphql-Java made that a protected method so that we could override it with our own logic:
https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/SimpleDataFetcherExceptionHandler.java#L40-L48
However, it is not easy to embed it with kickstart library right now.
Describe the solution you'd like
Expecting a non-required bean for
DataFetcherExceptionHandler
, so that it could be passed into the below places when building Execution strategy:graphql-spring-boot/graphql-spring-boot-autoconfigure/src/main/java/graphql/kickstart/spring/web/boot/GraphQLWebAutoConfiguration.java
Lines 177 to 178 in 13cd484
Describe alternatives you've considered
As a workaround, I have to provide my own bean for
executionStrategies
, which I feel is too much layer above:graphql-spring-boot/graphql-spring-boot-autoconfigure/src/main/java/graphql/kickstart/spring/web/boot/GraphQLWebAutoConfiguration.java
Line 113 in 13cd484
The text was updated successfully, but these errors were encountered: