使用 useReducer 处理复杂状态逻辑
用单个 useReducer 替代多个 useState 调用，编写包含操作类型的归约器函数，并从界面事件中分派操作。
使用 useReducer 处理复杂状态逻辑 是 CoddyKit 上的免费 React Native Academy 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 React Native Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 React Native Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why useReducer?
When a component has several useState calls whose updates are interrelated, the logic can become hard to follow. useReducer centralizes all state transitions in a single reducer function, making complex state logic easier to understand, test, and debug — the same pattern made popular by Redux.
The Reducer Function
A reducer is a pure function that takes the current state and an action object, and returns the next state. It must be pure — no side effects, no API calls, no mutations of the incoming state object. Return a new object for the new state. The action.type string identifies what transition to perform.
function counterReducer(state, action) {
switch (action.type) {
case 'increment':
return { count: state.count + 1 };
case 'decrement':
return { count: state.count - 1 };
case 'reset':
return { count: 0 };
default:
return state;
}
}Calling useReducer
useReducer takes the reducer function and an initial state, and returns [state, dispatch]. The state is the current state value. The dispatch function sends an action to the reducer to trigger a state transition and schedule a re-render.
import { useReducer } from 'react';
const initialState = { count: 0 };
function Counter() {
const [state, dispatch] = useReducer(counterReducer, initialState);
return (
<View>
<Text>Count: {state.count}</Text>
<Button title='+' onPress={() => dispatch({ type: 'increment' })} />
<Button title='-' onPress={() => dispatch({ type: 'decrement' })} />
<Button title='Reset' onPress={() => dispatch({ type: 'reset' })} />
</View>
);
}Passing Payload with Actions
Actions can carry additional data in a payload property. The reducer reads action.payload to know the specifics of the transition. For example, an 'addItem' action can carry the new item's data in its payload, which the reducer appends to the state's items array.
function listReducer(state, action) {
switch (action.type) {
case 'addItem':
return { items: [...state.items, action.payload] };
case 'removeItem':
return { items: state.items.filter((i) => i.id !== action.payload.id) };
default:
return state;
}
}
// Dispatch with payload
dispatch({ type: 'addItem', payload: { id: '1', text: 'Buy milk' } });Managing a Shopping Cart
A shopping cart is a great real-world use case for useReducer because it involves multiple related state transitions: adding items, removing items, updating quantities, and clearing the cart. Each action type maps to a clear, testable transition in the reducer function.
const initialCartState = { items: [], total: 0 };
function cartReducer(state, action) {
switch (action.type) {
case 'ADD':
return {
items: [...state.items, action.payload],
total: state.total + action.payload.price,
};
case 'CLEAR':
return initialCartState;
default:
return state;
}
}Initializing State Lazily
Pass a third argument to useReducer — an init function — to compute the initial state lazily. React calls init(initialArg) instead of using initialArg directly. This is useful when the initial state is derived from a prop or requires an expensive computation.
function init(initialCount) {
return { count: initialCount };
}
function Counter({ startCount }) {
const [state, dispatch] = useReducer(
counterReducer,
startCount, // passed to init
init // called once on mount
);
}useReducer vs useState
Use useState for simple, independent values (a boolean, a string, a number). Reach for useReducer when state transitions depend on multiple values at once, when the next state depends on the current state in complex ways, or when you want to co-locate all state logic in one testable function.
// useState — fine for simple independent values
const [name, setName] = useState('');
const [age, setAge] = useState(0);
// useReducer — better when these fields relate to each other
const [userForm, dispatch] = useReducer(userFormReducer, {
name: '',
age: 0,
isValid: false,
});Form State with useReducer
A complex registration form with many fields and validation logic benefits from useReducer. Define action types like 'CHANGE_FIELD', 'VALIDATE', and 'SUBMIT'. The reducer handles all field updates and validation in one place instead of scattered across multiple useState setters and useEffect calls.
function formReducer(state, action) {
switch (action.type) {
case 'CHANGE_FIELD':
return {
...state,
values: { ...state.values, [action.field]: action.value },
errors: { ...state.errors, [action.field]: null },
};
case 'SET_ERROR':
return { ...state, errors: { ...state.errors, ...action.errors } };
default:
return state;
}
}Testing a Reducer in Isolation
Because reducers are pure functions with no side effects, they are extremely easy to unit test. Call the reducer directly with a state and an action, and assert on the returned state. You do not need to mount any component or mock any API to test the logic.
// Pure unit test — no React needed
test('increment action increases count by 1', () => {
const state = { count: 5 };
const next = counterReducer(state, { type: 'increment' });
expect(next.count).toBe(6);
});
test('reset returns count to 0', () => {
const state = { count: 100 };
const next = counterReducer(state, { type: 'reset' });
expect(next.count).toBe(0);
});Combining useReducer with useContext
A powerful pattern is pairing useReducer with useContext to build a mini Redux-like global store. Export the dispatch function via context so any descendant component can dispatch actions without prop drilling. This avoids installing a third-party library for moderate complexity apps.
const StoreContext = createContext(null);
const DispatchContext = createContext(null);
export function StoreProvider({ children }) {
const [state, dispatch] = useReducer(appReducer, initialState);
return (
<StoreContext.Provider value={state}>
<DispatchContext.Provider value={dispatch}>
{children}
</DispatchContext.Provider>
</StoreContext.Provider>
);
}Dispatching from Multiple Components
With the dispatch function available via context, any nested component can trigger state transitions without receiving props. Import the useContext(DispatchContext) hook, call dispatch with the appropriate action type, and the reducer handles the update centrally. This scales well as the app grows.
function AddToCartButton({ product }) {
const dispatch = useContext(DispatchContext);
return (
<Button
title='Add to Cart'
onPress={() => dispatch({ type: 'ADD', payload: product })}
/>
);
}Quick Check
Test your understanding of useReducer for complex state logic from this lesson.
Lesson Recap
In this lesson you learned: useReducer centralizes state transitions in a pure reducer function, dispatch actions with a type and optional payload to trigger transitions, and pair useReducer with useContext for a scalable global state pattern without Redux. Next up we explore useCallback and useMemo for performance optimization.
常见问题解答
「使用 useReducer 处理复杂状态逻辑」课时是免费的吗？
是的 — 「使用 useReducer 处理复杂状态逻辑」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 React Native Academy 课程的其余内容，请升级到 CoddyKit PRO。 React Native Academy 课程共包含 4 节课。
「使用 useReducer 处理复杂状态逻辑」这节课中我会学到什么？
用单个 useReducer 替代多个 useState 调用，编写包含操作类型的归约器函数，并从界面事件中分派操作。 你通过在浏览器中直接运行的动手代码来练习 React Native Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 React Native Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 React Native Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「使用 useReducer 处理复杂状态逻辑」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 React Native Academy 课中编写并运行代码吗？
能。每节 React Native Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 使用 useRef 引用 DOM 节点与可变值
- 使用 useReducer 处理复杂状态逻辑
- 使用 useCallback 与 useMemo 提升性能
- 编写自定义钩子