Deleting Resources
Redux Resource provides four action types for deleting resources asynchronously. They are:
1
"DELETE_RESOURCES_PENDING"
2
"DELETE_RESOURCES_FAILED"
3
"DELETE_RESOURCES_SUCCEEDED"
4
"DELETE_RESOURCES_IDLE"
Copied!
Each request will always begin with an action with type DELETE_RESOURCES_PENDING. Then, one of the other three action types will be used to represent the resolution of that request. Use the other action types in the following way:
  • DELETE_RESOURCES_FAILED: Use this if the request fails for any reason. This
    could be network errors, or any
    greater than or equal to 400.
  • DELETE_RESOURCES_IDLE: Use this when the request is aborted.
  • DELETE_RESOURCES_SUCCEEDED: Use this when the request was successful.

Request Objects

Specifying a request key on the actions will create a request object in the store for this request. This object can be used to look up the status of the request.
Although it is recommended that you specify a request key whenever possible, there are some situations when you may not need to when deleting resources.
Because you usually know the ID of the resources that you're deleting, you may not need to specify a request key for delete operations. The metadata for the delete request can just be stored on the resource metadata directly.
For delete requests that affect multiple resources, it is typically preferable to specify a request key.

Successful Deletes

When an action of type DELETE_RESOURCES_SUCCEEDED is dispatched, three things will happen:
  1. 1.
    The resources included in the action will be replaced with null in the resources section of your resource slice.
  2. 2.
    The resources included in the action will be removed from all lists in the resource slice.
  3. 3.
    The value of deleteStatus will be set to "SUCCEEDED". All other meta values will be set to the default meta for that resource slice.

Redux Resource XHR

Redux Resource XHR provides an action creator that simplifies making CRUD requests. If you'd like to build your own, then that's fine, too. The example below may help.

Example Action Creator

This example shows an action creator to delete a single book. It uses the redux-thunk middleware and the library xhr for making requests.
1
import { actionTypes } from 'redux-resource';
2
import xhr from 'xhr';
3
4
export default function deleteBook(bookId) {
5
return function(dispatch) {
6
dispatch({
7
type: actionTypes.DELETE_RESOURCES_PENDING,
8
resourceType: 'books',
9
resources: [bookId],
10
});
11
12
const req = xhr.del(
13
`/books/${bookId}`,
14
(err, res, body) => {
15
if (req.aborted) {
16
dispatch({
17
type: actionTypes.DELETE_RESOURCES_IDLE,
18
resourceType: 'books',
19
resources: [bookId],
20
});
21
} else if (err || res.statusCode >= 400) {
22
dispatch({
23
type: actionTypes.DELETE_RESOURCES_FAILED,
24
resourceType: 'books',
25
resources: [bookId],
26
requestProperties: {
27
statusCode: res.statusCode
28
}
29
});
30
} else {
31
dispatch({
32
type: actionTypes.DELETE_RESOURCES_SUCCEEDED,
33
resourceType: 'books',
34
resources: [bookId],
35
requestProperties: {
36
statusCode: res.statusCode
37
}
38
});
39
}
40
}
41
);
42
43
return req;
44
}
45
}
Copied!