I noticed that the noThrow flag only disable throwing for GraphQL errors in the response. For HTTP errors codes coming back from the server an error will be thrown currently even though you set the flag.
In my opinion it makes sense to do the same for HTTP errors in the response. You either handle all the errors yourself or you let the middleware stack throw errors.
I noticed that the noThrow flag only disable throwing for GraphQL errors in the response. For HTTP errors codes coming back from the server an error will be thrown currently even though you set the flag.
In my opinion it makes sense to do the same for HTTP errors in the response. You either handle all the errors yourself or you let the middleware stack throw errors.