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
Currently when you use graphql you only have one choice of error, and that is a graphql error that comes with the response. If you have a network connectivity error or trying to request from the wrong url or something you'd usually receive a http error.
Currently graphql.query or graphql.mutation do not expect errors from typeof HttpResponse.error() although they are possible.
The improvement is to extend the error type for allowed graphql responses to also be of type HttpResponse.error() or compatible.
The text was updated successfully, but these errors were encountered:
Thanks for opening this, @hinogi. This appears to be a duplicate of #2130, which even has a pull request open. Please see that issue for more details. Thanks.
Scope
Improves an existing behavior
Compatibility
Feature description
Currently when you use graphql you only have one choice of error, and that is a graphql error that comes with the response. If you have a network connectivity error or trying to request from the wrong url or something you'd usually receive a http error.
Currently graphql.query or graphql.mutation do not expect errors from
typeof HttpResponse.error()
although they are possible.The improvement is to extend the error type for allowed graphql responses to also be of type HttpResponse.error() or compatible.
The text was updated successfully, but these errors were encountered: