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
{{ message }}
Repository navigation
Commit c3a8c19
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(mobile): workspace tabs, home filters and connection status derive instead of syncing
The workspace tab controller, the Android root context, the home list
filters and the connection-status delay each kept React state in step with
something else through an effect: a layout effect copying the selected tab
or navigation state into a ref, a render-phase dispatch moving the selection
off a hidden tab, an effect persisting the list scope after it changed, and
two timers driving the status fade.
- WorkspaceTabsContext: the selection lives in a per-provider atom and the
hidden-tab fallback is derived from preferences in a second atom, so
handlers read the current selection from the registry at call time. Drops
the layout effect and the render-phase dispatch.
- AndroidWorkspaceTabsProvider: the rail reads the root state from
rootNavigationRef when a tab is pressed instead of a ref updated in a
layout effect; the context only carries key and settingsOpen.
- home-list-options: the scope is saved from the handler that changes it.
- WorkspaceConnectionTitle: the show delay and fade are deadlines on the
shared clock store (useDeadlinePassed) instead of two timers.
- WorkspaceToolbar (generic variant): Back uses the shared useHardwareBack.
Effects: WorkspaceTabsContext 1 -> 0, AndroidWorkspaceTabsProvider 1 -> 0,
home-list-options 1 -> 0, WorkspaceConnectionTitle 2 -> 1 (the Animated fade
stays), WorkspaceToolbar 3 -> 2 (focus-after-commit effect stays).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments