A simple solution to our problem was essentially adding a match on the extraReducer builder for any thunk that included “:load” in its name, and then setting the appropriate loading state for the thunk in there. redux-saga 1.2.1 which has 1051172 weekly downloads.
We were using with createSlice and createAsyncThunk. Comparing trends for reduxjs/toolkit 1.8.6 which has 2068839 weekly downloads and 8582 GitHub stars vs.
To work with the actual result i (fullfilled, rejected) inside the component i need to use 'unwrapresult' from reudx toolkit.
When using Redux Persist without using the Thunk middleware, we‘d get an error in the browser’s console reading a non-serializable value was detected in the state. There are 6 async Thunks to be exported: createTutorial retrieveTutorials updateTutorial deleteTutorial deleteAllTutorials findTutorialsByTitle slices / tutorials. Before createAPI came out, my current team needed a way of cleaning up all of the loading logic around our async thunks. Redux Thunk middleware allows you to write action creators that return a function instead of an action. However the 'createAsyncThunk' always returns fullfilled. In the modification to the store above, we also included the Thunk middleware, which will intercept and stop non-serializable values in action before they get to the reducer. We also need to use Redux Toolkit createAsyncThunk which provides a thunk that will take care of the action types and dispatching the right actions based on the returned promise.
0 kommentar(er)
