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
This might be more of a feature request, but I noticed that when nesting queries or writing queries that will result in multiple queries, if one fails, the entire operation errors and there is no way to retrieve the data, that was returned from the API successfully.
An example would be retrieving user information from the API and then querying for all comments that user has posted. That can be written in 1 graphQL query but will result in multiple REST API calls. If one of them fails, the whole query fails without being able to retrieve at least part of the data.
I played around with the error handlers, but didn't get around the issue. What I would like is the data to be returned with an object that includes error information about all calls that failed.
Someone has an idea how to make that possible?
The text was updated successfully, but these errors were encountered:
This might be more of a feature request, but I noticed that when nesting queries or writing queries that will result in multiple queries, if one fails, the entire operation errors and there is no way to retrieve the data, that was returned from the API successfully.
An example would be retrieving user information from the API and then querying for all comments that user has posted. That can be written in 1 graphQL query but will result in multiple REST API calls. If one of them fails, the whole query fails without being able to retrieve at least part of the data.
I played around with the error handlers, but didn't get around the issue. What I would like is the data to be returned with an object that includes error information about all calls that failed.
Someone has an idea how to make that possible?
The text was updated successfully, but these errors were encountered: