Orange marks account trouble and the Manager, not only sessions that need you

Open Beginner friendly
#403 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
swift
Domain
design

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

priority: low

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

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.triangle badge 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.checkmark or bubble.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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haacked/switchboard

All issues in haacked/switchboard

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.