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
when GQL client throws , the function const raDataProvider = (raFetchType, resource, params) => { ...} in index.js should return a rejected promise, per data provider requirements in react-admin.
What happened instead:
While a
catch (e) {
return Promise.reject(e);
}
was added, this code is never reached since the promise chain already returned earlier, so the error is not caught, eg:
What you were expecting:
const raDataProvider = (raFetchType, resource, params) => { ...}
inindex.js
should return a rejected promise, per data provider requirements in react-admin.What happened instead:
While a
was added, this code is never reached since the promise chain already returned earlier, so the error is not caught, eg:
Solution is to add to each promise chain individually:
to ensure a rejected promise is returned with an error object with the required syntax.
This was seen together with #5907
The text was updated successfully, but these errors were encountered: