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
I see many requests to handle errors differently. Some simple, some quite involved.
However by simply changing the method GraphQLServlet.createResultFromDataAndErrors from private to protected access, it would be possible for subclasses to override and implement alternative error reporting/handling strategies.
My case is one of the simple ones. I would like to pass the executionId back to the client regardless of whether it is a "client error" or not. This allows me to tie an error in my browser console back to a server log.
The text was updated successfully, but these errors were encountered:
I see many requests to handle errors differently. Some simple, some quite involved.
However by simply changing the method GraphQLServlet.createResultFromDataAndErrors from private to protected access, it would be possible for subclasses to override and implement alternative error reporting/handling strategies.
My case is one of the simple ones. I would like to pass the executionId back to the client regardless of whether it is a "client error" or not. This allows me to tie an error in my browser console back to a server log.
The text was updated successfully, but these errors were encountered: