Skip to content

Way to distinguish graphql's errors from resolvers' internal errors #312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dimuls opened this issue Apr 9, 2018 · 0 comments
Open

Way to distinguish graphql's errors from resolvers' internal errors #312

dimuls opened this issue Apr 9, 2018 · 0 comments

Comments

@dimuls
Copy link

dimuls commented Apr 9, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant