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 was archived by the owner on Dec 19, 2023. It is now read-only.
Describe the bug
After upgrading from 8.0.0 to 8.1.0 the custom exceptions stopped working and all graphql errors are being converted back to the default "Internal server error" message.
To Reproduce
Steps to reproduce the behavior:
Expose a bean with @ExceptionHandler methods to create GraphQLError in case of certain exceptions
Describe the bug
After upgrading from 8.0.0 to 8.1.0 the custom exceptions stopped working and all graphql errors are being converted back to the default "Internal server error" message.
To Reproduce
Steps to reproduce the behavior:
@ExceptionHandler
methods to createGraphQLError
in case of certain exceptionsgraphql.servlet.exception-handlers-enabled: true
Expected behavior
Instead of the default GraphQLError I'd expect my custom error to be returned.
The text was updated successfully, but these errors were encountered: