-
Notifications
You must be signed in to change notification settings - Fork 44
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
adding extensions to ExecutionError #53
Comments
Sounds like a good idea! PRs welcome. |
The JSON.parse(execution_error.response.body, symbolize_names: true)[:extensions] If you are requesting to add an alias, then yes, that seems like a useful helper method. However, if you meant to mutate the |
@yuki24 I know it's only recommended https://facebook.github.io/graphql/draft/#example-fce18 at the moment but as I see everybody is using it (from startups to big companies). Thanks for the example on how to parse the keys. I think it's a bit awkward though. It seems to be way easier to use @dblock Let me know if you still want me to open a PR based on @yuki24 's comments. |
@RealSilo PRs always welcome! |
Sounds good. I will try to open a PR this weekend. |
Hey,
I think it would be great to have
extensions
withcode
(see here: http://graphql-ruby.org/errors/execution_errors.html) to theGraphlient::Errors::ExecutionError
class.So it could be used in tests as:
The text was updated successfully, but these errors were encountered: