Three components with no shared parent and no parameters between them read and write one piece of state.
How it works
Try it: click +1 and +2 and watch the render counters.
ClickStateis a record implementingIState<ClickState>. The root hub creates it on first use fromClickState.Initial.ClickButtonswrites withState<ClickState>().Update(...). It never reads the state reactively, so it only re-renders after its own clicks (normal Blazor behavior for event handlers).ClickDisplaydeclares[UseState] private partial ClickState Clicks { get; }and re-renders on every change.ParityBadgeuses a selector,SelectIsEven. +2 doesn't change parity, so it doesn't re-render.- Set same value writes an equal record. Record equality turns that into a no-op, so nothing re-renders.