Skip to content

feat(web): add Schedules nav to the session header - #116

Merged
setkyar merged 2 commits into
ygncode:mainfrom
setkyar:feat/session-header-schedules
Sep 16, 2026
Merged

setkyar merged 2 commits into
ygncode:mainfrom
setkyar:feat/session-header-schedules

Conversation

@setkyar

@setkyar setkyar commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Why

Schedules were only reachable from the sessions index. Opening /schedules from an active conversation meant going back to the list first.

What

  • Add a Schedules control to the session header, immediately left of + New (the same calendar-clock + label used on the index).
  • Icon-only on viewports ≤900px, matching + New.
  • Add Schedules to the session ⋯ menu next to Settings.
  • Internal ⋯ menu links (/schedules, /settings) now use SPA navigation instead of a full page load.

Tests

  • SessionHeader.test.js — header control sits left of + New and navigates to /schedules.
  • CommandMenu.test.js — ⋯ menu includes the schedules link and navigates.
  • e2e/tests/schedules.spec.ts — session header button opens the schedules page.

npx vitest run src/components/session/SessionHeader.test.js src/components/session/CommandMenu.test.js passes.

Schedules were only reachable from the sessions index, so opening one
from an active session meant leaving the conversation first. Put the
same control next to + New (and in the session ⋯ menu) so /schedules
is one click away.
Schedules copied the + New chip layout into a second 900px block.
Share the compact-header layout and fold the breakpoint together.

Close the session ⋯ menu before SPA navigation, matching HomeMenu, so
the popover does not linger if the page ever stops unmounting.
@setkyar
setkyar merged commit ac71eb5 into ygncode:main Sep 16, 2026
3 checks passed
@setkyar
setkyar deleted the feat/session-header-schedules branch September 16, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant