August 28, 2026
Put a draft where its lifetime belongs
A row's local state is useful while that row remains mounted. Filtering can remove the row entirely. Giving it a stable key does not, by itself, promise to preserve state after unmounting.

Decide what must survive

If the user expects an unfinished note to return after clearing a filter, store the draft with the record ID in application state. Let the row observe and edit that value through reducers.

Keep the boundary small

Hover state or an isolated open disclosure can remain local. The choice follows the information's lifetime and ownership, rather than a rule that all mutable values belong in one global structure.
Back to blog