-
Notifications
You must be signed in to change notification settings - Fork 182
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
Support 'path' in error reporting #127
Comments
Looks like Luckily Flask-GraphQL + |
A humble beginning:
With my simple schema right now I can only get errors on top-level fields, and Accidentally found a way to get the alias supported. Missing root value name. So perhaps something needs to be patched so that GraphQLError would see the whole tree / path. However even this small patch helps me to debug the problems more easily. My query is generated based on user request, and end-user doesn't actually know GraphQL is used (and shouldn't know about its syntax at all). |
I started adding this feature at graphql-python/graphql-core#148 |
I can try the patches late this week / early next week, when getting back to the related project (for graphene 2.0 upgrades) |
Fixed in #186 |
When dealing with error responses on client side, would be nice to know which field caused it. Right now there seems to be support for
locations
->(column: .., line: ...)
, but not for thepath
specified in graphql/graphql-spec#230Note: might take a look at this at some point myself (would like to also fine-tune when server side exception prints traceback to logs and/or figuring out how to gracefully report errors to client without exception + traceback on server...)
The text was updated successfully, but these errors were encountered: