Fetch: Handling Non-OK Status Codes with Rejection and Error Catching
The provided code utilizes the 'whatwg-fetch' polyfill within Redux and redux-promise-middleware for data retrieval. However, the issue lies in handling non-OK status codes (4xx and 5xx), as Fetch promises typically only reject on network errors.
Rejection Handling
To ensure rejection of the promise with a custom error message for non-OK status codes, consider the following approach:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
Error Catching
Within the action creator, an error is thrown when the response status is non-OK, and this error can be caught when handling the action in the reducer.
Sample Reducer:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
In this updated code, the payload of the 'FETCH_VEHICLE_REJECTED' action will contain the error message created in the action creator. This allows for proper error handling and display within the application.
The above is the detailed content of How to Handle Non-OK Status Codes with Fetch in Redux and redux-promise-middleware?. For more information, please follow other related articles on the PHP Chinese website!