Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Passing Error to payloadCreator
See original GitHub issueCurrently it’s not possible to pass Error object to payloadCreator because it’s intercepted by this line.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Accessing the original error in createAsyncThunk #390 - GitHub
With the current implementation of createAsyncThunk, there is no way to access any errors returned from a server.
Read more >Handling errors with redux-toolkit - Stack Overflow
We use thunkAPI, the second argument in the payloadCreator; containing all of the parameters that are normally passed to a Redux thunk ...
Read more >createAsyncThunk - Redux Toolkit
The payloadCreator function will be called with two arguments: arg : a single value, containing the first parameter that was passed to the ......
Read more >Using Redux Toolkit's createAsyncThunk - LogRocket Blog
Handling errors in createAsyncThunk ; payloadCreator returns a rejected promise, the ; rejected action is dispatched (with action.payload as ...
Read more >createAsyncThunk in Redux-Toolkit | by Abhimanyu Chauhan
pending: before the callback is called in the payloadCreator ... the requestId and the args passed to the payloadCreator, error in case of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any news on this ?
I’ve been super slammed lately and haven’t had a chance to do enough digging here. If you’re willing to make a PR removing that line + make sure it doesn’t break existing behavior I’d be happy to merge it.