Deleting Resources
Last updated
Last updated
Redux Resource provides four for deleting resources asynchronously. They are:
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.
Specifying a on the actions will create a request object in the store for this request. This object can be used to look up the 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.
When an action of type DELETE_RESOURCES_SUCCEEDED
is dispatched, three things will happen:
The resources
included in the action will be replaced with null
in the resources
section of your resource slice.
The resources
included in the action will be removed from all lists in the resource slice.
The value of deleteStatus
will be set to "SUCCEEDED"
. All other meta values will be set to the default meta for that resource slice.
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.
This example shows an action creator to delete a single book. It uses the middleware and the library for making requests.