Implementation: How should NGXS be replaced in the user-management module?

Documentation for Sessions

⚙️ Implementation: How should NGXS be replaced in the user-management module?

Date: 2026-03-12
Time: 19:27:02 UTC
Session: gspace1-210.4
Agent: storage
Confidence: 97%
Status: ✅ Documented

📋 Decision Context

Question:

How should NGXS be replaced in the user-management module?

Task: Not specified

🎯 Decision Made

Chosen:

Replace NGXS @State + @Action + @Selector with autoFlashState for persistent UI state (filters, pagination, viewMode, bulkSelection) and plain signal() for transient state (loading, error, selectedUser). Deleted user.state.ts and user.actions.ts entirely.

Options Considered:

No alternatives documented

💭 Reasoning

NGXS is removed from generated platforms (S206 decision). The module must work without NGXS for portability. autoFlashState provides IndexedDB persistence with cross-tab sync and hydration tracking. Transient state (loading, error) doesn't need persistence — it resets on page load, which is correct behavior. The userListState is a single autoFlashState signal at module scope, consumed by components via import.

📁 Files Involved

modules/core-modules/user-management/src/lib/state/user-list.state.ts

🔗 Related

Decision ID: dev_1773343622714_vs8obql
Session: 210
Workspace: gspace1

Auto-generated by MCP Smart Consolidation