psa-systems/mokosh-apps
Watch
9
0
Fork
You've already forked mokosh-apps
 0
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

feat(spa): collapse sidebar to Dashboard-only while server is down #417

Merged
Claude-Run merged 1 commit from feat/MAPPS-358-server-down-sidebar into main 2026-07-04 03:32:04 +02:00
Conversation 0 Commits 1 Files changed 1 +56
Claude-Run commented 2026-07-04 03:30:00 +02:00
Member
Copy link

While mokosh-server is unreachable, the data-driven pages already swap in the MAPPS-351 ContentUnavailable "cannot connect / return to dashboard" body (retrofitted across pages in MAPPS-357) and the MAPPS-333 outage banner sits above the layout. The sidebar, however, still offered every section, so a user could click into any destination during an outage only to land on the same "can't load this page" state - dead-end navigation.

Collapse the sidebar to just the Dashboard entry whenever the server is unreachable, leaving the one coherent place to keep the user (matching the outage page's "return to dashboard" affordance). SidebarContent reads the MAPPS-333 reachability flag via use_server_reachable, so the rail collapses the instant the server goes down and every section returns the instant the recovery poll flips the flag back. Both the desktop rail and the mobile drawer inherit this since they share SidebarContent.

The down/recovery decision is factored into the pure full_nav_visible(server_reachable) predicate, mirroring the classify_remote idiom, so the transitions are unit-testable without a renderer. A test walks reachable -> down (Dashboard-only) -> recovered (full nav restored).

#MAPPS-358

While mokosh-server is unreachable, the data-driven pages already swap in the MAPPS-351 ContentUnavailable "cannot connect / return to dashboard" body (retrofitted across pages in MAPPS-357) and the MAPPS-333 outage banner sits above the layout. The sidebar, however, still offered every section, so a user could click into any destination during an outage only to land on the same "can't load this page" state - dead-end navigation. Collapse the sidebar to just the Dashboard entry whenever the server is unreachable, leaving the one coherent place to keep the user (matching the outage page's "return to dashboard" affordance). SidebarContent reads the MAPPS-333 reachability flag via use_server_reachable, so the rail collapses the instant the server goes down and every section returns the instant the recovery poll flips the flag back. Both the desktop rail and the mobile drawer inherit this since they share SidebarContent. The down/recovery decision is factored into the pure full_nav_visible(server_reachable) predicate, mirroring the classify_remote idiom, so the transitions are unit-testable without a renderer. A test walks reachable -> down (Dashboard-only) -> recovered (full nav restored). #MAPPS-358
feat(spa): collapse sidebar to Dashboard-only while server is down
All checks were successful
Check / fmt + clippy + tests (pull_request) Successful in 1m37s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
f1da628b36 
While mokosh-server is unreachable, the data-driven pages already swap in the MAPPS-351 ContentUnavailable "cannot connect / return to dashboard" body (retrofitted across pages in MAPPS-357) and the MAPPS-333 outage banner sits above the layout. The sidebar, however, still offered every section, so a user could click into any destination during an outage only to land on the same "can't load this page" state - dead-end navigation.

Collapse the sidebar to just the Dashboard entry whenever the server is unreachable, leaving the one coherent place to keep the user (matching the outage page's "return to dashboard" affordance). SidebarContent reads the MAPPS-333 reachability flag via use_server_reachable, so the rail collapses the instant the server goes down and every section returns the instant the recovery poll flips the flag back. Both the desktop rail and the mobile drawer inherit this since they share SidebarContent.

The down/recovery decision is factored into the pure full_nav_visible(server_reachable) predicate, mirroring the classify_remote idiom, so the transitions are unit-testable without a renderer. A test walks reachable -> down (Dashboard-only) -> recovered (full nav restored).

#MAPPS-358
Claude-Run deleted branch feat/MAPPS-358-server-down-sidebar 2026-07-04 03:32:04 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!417
No description provided.