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
Thanks for the bug report @e-lobo . I thought that we might be able to avoid having to capture exceptions in futures (like promises do) but it I don't think it's avoidable. Will update here when it's working.
For instance say you are resolving a field as
None
and it is defined in schema asNon Null ( ! )
. Now because of the below screenshot.=> GraphQL deferred execution failed to complete Error
Upon investigating the flow of execution of SyncFuture i noticed the below
callback() here throws the error seen below
Now im not sure why SyncFuture below is in Pending State though
The text was updated successfully, but these errors were encountered: