State management in Blazor
summary
Demos compare four concrete approaches: a root CascadingParameter component that keeps a boolean and preserves toggles across pages while Blazor only re-renders affected components (timestamps show selective renders); a DI-backed state object registered as scoped state service with explicit change events and IDisposable wiring; an MVVM-style view model injected via DI to centralize logic; and a full Flux implementation using the Fluxor + Redux DevTools pipeline (immutable record state, actions, reducers, effects, dispatcher) that enables time‑travel debugging but adds notable boilerplate and memory/complexity tradeoffs.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:38Why Would We Use State Management
- 3:43What Can You Do with State Management
- 5:48Cascading State Parameter
- 6:32Cascading Element
- 14:21Menu Toggler Control
- 16:44A State Machine What Is the State Machine
- 19:40Dependency Injection
- 26:03Mvvm Pattern
- 27:05The View Model
- 34:57Mvvm
- 36:47Flux Pattern
- 42:29Override the Get Initial State
- 50:50Fetch Data
related talks
42mState Management in Blazor Apps
49mBuilding Event Driven User Interfaces
49mArchitecting Blazor applications – An Angular inspired approach
49mArchitecting Blazor applications – An Angular inspired approach
41mThe Battle of State Management in modern frontend applications
52mState management beyond the libraries
43mState Manager Architecture
25mEnemy of the State