Skip to main content

rerender-functional-setstate

Use functional setState updates to prevent stale closures and unnecessary callback recreations. Apply when updating state based on the current state value in React components.

소스 정보

저장소
TheOrcDev/8bitcn-ui
최근 소스 활동
2026년 1월 16일 09:09
감지된 SKILL.md 언어
영어
스타
2,061
포크
119

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
rerender-functional-setstate
description
Use functional setState updates to prevent stale closures and unnecessary callback recreations. Apply when updating state based on the current state value in React components.
## Use Functional setState Updates When updating state based on the current state value, use the functional update form of setState instead of directly referencing the state variable. This prevents stale closures, eliminates unnecessary dependencies, and creates stable callback references. **Incorrect (requires state as dependency):** ```tsx function TodoList() { const [items, setItems] = useState(initialItems) // Callback must depend on items, recreated on every items change const addItems = useCallback((newItems: Item[]) => { setItems([...items, ...newItems]) }, [items]) // items dependency causes recreations // Risk of stale closure if dependency is forgotten const removeItem = useCallback((id: string) => { setItems(items.filter(item => item.id !== id)) }, []) // Missing items dependency - will use stale items! return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} /> } ``` The first callback is recreated every time `items` changes, which can cause child components to re-render unnecessarily. The second callback has a stale closure bug—it will always reference the initial `items` value. **Correct (stable callbacks, no stale closures):** ```tsx function TodoList() { const [items, setItems] = useState(initialItems) // Stable callback, never recreated const addItems = useCallback((newItems: Item[]) => { setItems(curr => [...curr, ...newItems]) }, []) // No dependencies needed // Always uses latest state, no stale closure risk const removeItem = useCallback((id: string) => { setItems(curr => curr.filter(item => item.id !== id)) }, []) // Safe and stable return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} /> } ``` **Benefits:** 1. **Stable callback references** - Callbacks don't need to be recreated when state changes 2. **No stale closures** - Always operates on the latest state value 3. **Fewer dependencies** - Simplifies dependency arrays and reduces memory leaks 4. **Prevents bugs** - Eliminates the most common source of React closure bugs **When to use functional updates:** - Any setState that depends on the current state value - Inside useCallback/useMemo when state is needed - Event handlers that reference state - Async operations that update state **When direct updates are fine:** - Setting state to a static value: `setCount(0)` - Setting state from props/arguments only: `setName(newName)` - State doesn't depend on previous value **Note:** If your project has [React Compiler](https://react.dev/learn/react-compiler) enabled, the compiler can automatically optimize some cases, but functional updates are still recommended for correctness and to prevent stale closure bugs.
GitHub에서 보기