View switching and history commands sit in the Session menu
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- swift
- Domain
- desktop, developer-experience
Research direction
Start with Sources/SwitchboardApp/App.swift, especially the Session command menu around lines 53–122 and the menu bar item around line 224. Review open PRs #376, #383, and #260 first because they also change App.swift; then check how SwiftUI defines the View and Go menus. Done when the listed view and navigation commands are in their requested menus, session actions remain in Session, and the quit label reads “Quit Switchboard”.
Written by the indexing model from the issue text.
Description
View switching and history commands live in the Session menu, mixed with actions on the selected session.
What happens
CommandMenu("Session") holds Show Inbox, Show Board, Show Issues, Filter by Org, Search, Next/Previous Session, Back, Forward, Show Recent Places, and the focus commands. Stop, Resume, Done, and Acknowledge are in the same menu. The menu bar item ends with "Quit" (App.swift:224), without the app's name.
Why it matters
Mac apps put view switching in the View menu and history in a Go menu (Finder, Xcode, Safari's History). A user looking for Back won't think to open a menu named Session. A menu bar item's quit command reads "Quit ".
Suggested fix
- Move Show Inbox, Board, and Issues, and Filter by Org, to
CommandGroup(after: .sidebar)in View. - Add a Go menu with Back, Forward, Recent Places, Next Needing You, and Next/Previous Session.
- Keep the Session menu for actions on the selected session.
- Rename the menu bar item's "Quit" to "Quit Switchboard".
This is finding 11 of the #295 UI once-over. Open PRs #376, #383, and #260 change App.swift, and #383 renames Filter by Org.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 308
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from haacked/switchboard
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
haacked/switchboard#420 ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
haacked/switchboard#403 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#395 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
haacked/switchboard#391 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
haacked/switchboard#419 ·
Maintainers usually reply within 1 day
All issues in haacked/switchboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Enzoo404/gravitybox#21 ·
Maintainers usually reply within 1 day
-
area: sidebar enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ZigaoWang/zigzag#351 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manaflow-ai/cmux#46584 ·
Maintainers usually reply within 1 day
-
android:core ios:core
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day