zustand

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: State: We are migrating slices from plain StateCreator objects to class-based actions . - Naming: Verb form ( createTopic , sendMessage ) - Responsibilities: Parameter validation, flow orchestration - Naming: internal_ prefix ( internal_createTopic ) - Responsibilities: Optimistic updates, service calls, error handling - Should not be called directly by UI - Naming: internal_dispatch + entity ( internal_dispatchTopic ) - Responsibilities: Calling reducers, updating store - Managing object lists/maps ( messagesMap , topicMaps ) - Optimistic updates - Complex state transitions - Toggling booleans - Updating simple values - Setting single state fields - Public: createTopic , sendMessage - Internal: internal_createTopic , internal_updateMessageContent - Dispatch: internal_dispatchTopic - Toggle: internal_toggleMessageLoading - ID arrays: messageLoadingIds , topicEditingIds - Maps: topicMaps , messagesMap - Active: activeTopicId - Init flags: topicsInit - Action patterns: references/action-patterns.md - Slice organization: references/slice-organization.md - Define a class that encapsulates actions and receives (set, get, api) in the constructor. - Use #private...