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 probably isn't an issue or an enhancement request. I am just trying to understand the thinking of returning only the statusCode and statusText when experiencing an error during fetch. Sometimes the API returns detailed information about what the problem is in the response body, and this strips it away. A third property which is the response body could expose that again.
Is this just implemented this was as it's a good starting point for most cases and a user of redux-api can easily implement their own adapter if they need different behaviour?
Hi @IronSean . Of cause redux-api was written as very customisable and very thin wrapper around redux and ajax providers like fetch api. And it's right way to write your own adapter if you have your specific needs
This probably isn't an issue or an enhancement request. I am just trying to understand the thinking of returning only the statusCode and statusText when experiencing an error during fetch. Sometimes the API returns detailed information about what the problem is in the response body, and this strips it away. A third property which is the response body could expose that again.
Is this just implemented this was as it's a good starting point for most cases and a user of redux-api can easily implement their own adapter if they need different behaviour?
redux-api/src/adapters/fetch.js
Line 29 in e760763
The text was updated successfully, but these errors were encountered: