Orange marks account trouble and the Manager, not only sessions that need you
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
Research direction
Start with AccountMenu.swift lines 34–35 and ContentView.swift lines 437–438 to trace the account trouble color and Manager symbol. Review the open pull requests #375, #382, and #383 that also change ContentView.swift before editing. Update the account indicator and Manager symbol as suggested, then confirm the toolbar uses orange only for sessions that need attention.
Written by the indexing model from the issue text.
Description
The toolbar uses the Needs-you orange for account trouble and for the Manager, so orange no longer means only "a session needs you".
What happens
- AccountMenu.swift:34-35: the account icon turns orange when a limit is spent or an account is signed out.
- ContentView.swift:437-438: the Manager button is a star that turns orange while a conversation waits.
Why it matters
The app uses orange to mean a session needs you, in the sidebar, the Inbox, and the Board. When the toolbar uses it for other things, a glance at the window says less. A star on macOS usually means a favorite, so it doesn't suggest the Manager.
Suggested fix
- Show account trouble as a yellow
exclamationmark.trianglebadge on the account item instead of the Needs-you color. - Give the Manager a symbol that reads as a person or a conversation, such as
person.crop.circle.badge.checkmarkorbubble.left.and.text.bubble.right.
This is finding 14 of the #295 UI once-over. Open PRs #375, #382, and #383 change ContentView.swift.
- 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
-
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
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
haacked/switchboard#412 · 1 comment ·
Maintainers usually reply within 1 day
All issues in haacked/switchboard
Similar issues
-
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
-
An exit-test child that can't find its exit test runs the whole suite (can fork-bomb)Possibly taken @grynspan claimed this today. Openai-assisted bug command-line experience exit-tests
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
swiftlang/swift-testing#2054 · 1 comment ·
Maintainers usually reply within 1 day