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
I have a batch resolver that throws an exception. The response then contains for every entry the same error (which is okay), but it's only a java.util.concurrent.CompletionException with error code completion, but I need access to the exception that caused the failure. It doesn't help to add the CompletionException to the smallrye.graphql.unwrapExceptions config.
The text was updated successfully, but these errors were encountered:
I think unwrapping the CompletionException should be okay for everybody: I can't think of any use case for seeing this technical detail. If someone objects, using the smallrye.graphql.unwrapException would be a fallback.
@t1 - I am battling to fix this. Have tried multiple approaches, but get stuck .... need to think about this a bit more....I am moving this to 1.0.22 (I need to do a release, and I am not going to be in time to get this in).
I have a batch resolver that throws an exception. The response then contains for every entry the same error (which is okay), but it's only a
java.util.concurrent.CompletionException
with error codecompletion
, but I need access to the exception that caused the failure. It doesn't help to add theCompletionException
to thesmallrye.graphql.unwrapExceptions
config.The text was updated successfully, but these errors were encountered: