zustand

Structure Zustand state management by defining public, internal, and internal_dispatch action layers to separate UI-facing actions from business logic and state-update reducers. This hierarchy keeps store updates clean and maintainable as your application grows.

Implement optimistic updates in Zustand by applying immediate UI state changes through internal_dispatch reducers, then running a safe refresh cycle to reconcile consistency. This pattern ensures responsive interfaces while preventing permanent state drift.

Compose Zustand class-based action slices using the flattenActions utility instead of object spreads. Spreading breaks prototype chains and private class-field behavior, whereas flattenActions safely merges class instances while preserving controlled method exposure.

Use Zustand set for simple direct state assignments, and use internal_dispatch reducers for complex state transitions involving optimistic update flows or map/array manipulation. This decision rule standardizes update logic and prevents inconsistent state mutations across slices.

Manage Zustand entity state using standardized messagesMap and topicMaps for data storage, and use loading ID arrays for tracking in-flight requests. This map-based design supports efficient optimistic create and update flows for chat topics.

Yes, this Zustand state management approach works with TypeScript by using class-based action migration with private constructor-bound accessors. This provides strict typing for slice composition and controlled public method exposure.