ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #redux
A decision guide that compares Redux Thunk and Redux Saga, outlines trade‑offs, and shows a concrete implementation with Redux Toolkit's createAsyncThunk.
Learn how Redux Toolkit's createSlice cuts boilerplate, lets you write mutable‑style reducers safely with Immer, and integrates async thunks—plus the trade‑offs to watch.
If your UI never updates after dispatching a Redux action, this diagnostic checklist pinpoints the root cause—direct mutation, selector pitfalls, missing Provider, middleware misconfig, and more—and offers concrete fixes for Redux Toolkit apps.
Learn how createSlice generates action creators and reducers, integrates with Immer, and works with DevTools—plus the trade‑offs to watch for.
Redux Toolkit's createSlice, powered by Immer, collapses the classic constants/actions/reducer ceremony into one file where reducers read like mutations but stay immutable. Here's how it works and what to watch for.
Learn how to use Redux Thunk to handle async actions, see a step‑by‑step example, and avoid common pitfalls like state mutation or infinite loops.
I'm wiring up RTK Query (via createApi in Redux Toolkit) and want queries to refetch when the browser window regains focus. The documentation describes refetchOnFocus as opt-in, and that setupListeners(store.dispatch) must be called for focus/reconnect events to reach the store. My uncertainty is about how the pieces interact before I commit to a configurati
Transitioning to createSlice Architecture Migrating a legacy Redux codebase to Redux Toolkit (RTK) involves shifting from manual action-type constants and switch-case reducers to the createSlice API. While RTK integrates Immer to allow mutating-style logic, legacy reducers still require strict immutability to prevent state corruption. A technical uncertainty
When using configureStore , developers can supply middleware as either a plain array or a callback that receives getDefaultMiddleware . The documentation notes that passing a plain array does not guarantee the relative order of custom middleware versus the default middleware chain ( serializableCheck , immutableCheck , thunk ). This creates uncertainty for m
react
javascript