You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the tracking issue for the Event System & State Management initiative — the largest architectural refactor for v1.0, touching event processing, state synchronization, and the developer-facing API.
Goals
Redesign EventHandler with a global registry, awaitable semantics, and partial-arg call convention
Extract dirty/accessed var tracking into a standalone mixin independent of rx.State
Introduce ~~EventContext~~ as the foundational execution primitive (owns state lock, manages backend event queue, tracks mutability scope)
Move the event queue to the backend, eliminating frontend round-trips for chained events
Make ~~rx.Field~~ a first-class descriptor enabling composable arbitrary states without ~~rx.State~~ inheritance
Activity
linear commentedon Mar 25, 2026
ENG-9179
/_reflex/prefix #6226opentelemetry-instrumentation-reflex: full-stack OTel package #6227rx.State#6228on_connectlifecycle hook for@rx.event#6229rx.Fieldsetter decorators with frontend compilation support #6230rx.Fieldchange observers (@field_name.on_changedecorator) #6231on_unloadlifecycle hook #6233new_tokenbehavior to allow multiple tabs sharing a single client_token #6252[-]Event System & State Management: Tracking Issue[/-][+]Event System: Tracking Issue[/+]new_tokenbehavior to allow multiple tabs sharing a single client_token #6252rx.State#6228/_reflex/prefix #6226rx.Fieldchange observers (@field_name.on_changedecorator) #6231rx.Fieldsetter decorators with frontend compilation support #6230