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
graphql.Result.Errors should give abiltiy to distinguish graphql's errors from resolvers' internal errors. We need this feature to be able to submit metrics about graphql errors to out monitor solution.
By graphql error i mean errors connected to bad syntax, parsing and resolving which are not caused by resolvers implementation. Such errors which are not originated in resolvers internals.
I think this feature request somehow related to #109.
In this graphql library both of this problem solved by forwarding original errors to handler level: i can type assert them, extract error codes, and modify errors structures returned by the server.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
graphql.Result.Errors
should give abiltiy to distinguish graphql's errors from resolvers' internal errors. We need this feature to be able to submit metrics about graphql errors to out monitor solution.By
graphql error
i mean errors connected to bad syntax, parsing and resolving which are not caused by resolvers implementation. Such errors which are not originated in resolvers internals.I think this feature request somehow related to #109.
In this graphql library both of this problem solved by forwarding original errors to handler level: i can type assert them, extract error codes, and modify errors structures returned by the server.
The text was updated successfully, but these errors were encountered: