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.
When graphql.servlet.exception-handlers-enabled is set to true, validation errors do not contain location, path, or extensions. This is true with and with out @ExceptionHandlers. In this scenario, my validation error is passing an integer to a parameter that requires a string.
When I set graphql.servlet.exception-handlers-enabled to false, location, path, and extensions appear normally in the results for validation errors.
As a test, I made my application throw an IllegalArgumentException and it was correctly picked up by my error handler and contained location, path, and extensions.
Uh oh!
There was an error while loading. Please reload this page.
Version: 8.0.0
When
graphql.servlet.exception-handlers-enabled
is set to true, validation errors do not contain location, path, or extensions. This is true with and with out@ExceptionHandler
s. In this scenario, my validation error is passing an integer to a parameter that requires a string.When I set
graphql.servlet.exception-handlers-enabled
to false, location, path, and extensions appear normally in the results for validation errors.As a test, I made my application throw an
IllegalArgumentException
and it was correctly picked up by my error handler and contained location, path, and extensions.For reference, here is my error handler:
The text was updated successfully, but these errors were encountered: