Homepage is the library; signal chain moves to settings; logo links home #173
No Assignees
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: yolo/arr#173
Reference in New Issue
Block a user
Implements the two navigation rulings from #169.
Depends on: #169
The library is the homepage.
/renders the library view. Theboardrouteis removed from
router.ts— it is not kept as an alias and not left reachable atanother path. Everywhere that currently navigates to
{ kind: "board" }as afallback or a return target navigates to the library instead: the Esc handler, the
cleared-search restore, the detail views' parent route, and the not-found fallback
in
parseRoute.The signal chain moves to settings. The
<main class="board">section — thefour modules and the bus traces between them — becomes a section of the settings
page, alongside roots and policies. The health poll that drives the lamps has to
keep running and keep painting them there. The master lamp stays on the rail
exactly as it is now, so the at-a-glance read does not depend on visiting
settings.
The wordmark links home.
arron the rail navigates to/. It is currently aplain
<h1>; give it a real activatable control with a keyboard-reachable focusstate, rather than a click handler on a heading. The rail's existing
librarynav button and the wordmark now go to the same place — that is fine and expected,
but check the
aria-pressedstate on the nav buttons still reads correctly oncelibrary is also the root route.
Watch for: the library view currently assumes it is entered from a nav click, so
confirm a cold load of
/populates it; and the search box restores the board onclear, which now means the library.
Scope:
web/index.html,web/src/router.ts,web/src/main.ts,web/src/settings.ts,web/src/style.css. Goes through theimpeccableskill — this is a navigation andlayout change, so drive the browser with
agent-browserand look at it.Non-goals: no change to what the library view itself renders, and no change to the
queues or settings content beyond receiving the diagram.
While verifying in the browser I hit a bug outside this issue's scope:
ratingChipinweb/src/main.tsguardsvote_average === nullbut notundefined. Against a daemon still serving the pre-#148 list schema (the one deployed on :7878 right now),/api/seriesomitsposter_path/vote_averageentirely, so expanding "show N satisfied" in the library throwsundefined.toFixedinformatRatingand the card groups render empty. Current arr-api always serializes the fields asnull, so this only bites a dev UI pointed at a stale daemon — but anypnpm devsession against the deployed instance will hit it until that daemon is redeployed.