zustand

Zustand state management patterns and conventions for LobeHub store development. Main interfaces for UI components: Core business logic implementation: State update handlers: Use Reducer Pattern: Use Simple set : Delete operations : Don't use optimistic updates (destructive, complex recovery) Actions: Public: createTopic , sendMessage Internal: internal_createTopic , internal_updateMessageContent Dispatch: internal_dispatchTopic State: ID arrays: topicEditingIds Maps: topicMaps , messagesMap Active: activeTopicId Init flags: topicsInit We are migrating slices from plain StateCreator objects to class-based actions . - Three-tier action hierarchy: public actions for UI, internal actions for business logic, and dispatch methods for state updates; use reducer pattern for complex state and simple set for primitives - Optimistic update pattern for non-destructive operations: update frontend immediately, call backend service, then refresh for consistency - Class-based action implementation using private fields and flattenActions for composition; migrate away from plain StateCreator objects toward encapsulated, type-safe action classes - Naming conventions for actions (verb form for public, internal_ prefix for logic, internal_dispatch* for updates) and state (ID arrays, maps, active flags, init flags) - Naming: Verb form ( createTopic , sendMessage ) - Responsibilities: Parameter...