-
Notifications
You must be signed in to change notification settings - Fork 65
rescue_from isn't working due to promises #17
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
Comments
So I ended end finding a way to make that works here's a code sample of how I do it.
From my understanding it is related to rmosolgo/graphql-ruby#1598 You have to call MySchema.enable_preloading at the end instead of inside the schema definition, also, I didn't try the reorder of rescue_from that they talked about since errors were already outside of the schema in our project. |
Edit: sorry, I thought this was an open PR on graphql-ruby 😬 |
Uh oh!
There was an error while loading. Please reload this page.
Using graphql-ruby 1.8.x, I cannot rescue errors from queries as I do for mutations due to batching and its Promises. How can i Handle that ?
for mutation this is working :
The text was updated successfully, but these errors were encountered: