There is no Settings window, so ⌘, doesn't open anything

Open
#399 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

Read Sources/SwitchboardApp/App.swift and the existing IssueSetupView to understand the app’s scenes and issue setup sheet. Then trace how sbd updates config.json and how the live cap, auto mode, and default account are represented. Done means a Settings scene has General, Issues, and Advanced tabs, changes go through sbd, and Advanced opens config.json.

Written by the indexing model from the issue text.

Description

Switchboard doesn't have a Settings window, so ⌘, doesn't open anything.

What happens

App.body declares the main window and a MenuBarExtra, but it doesn't have a Settings {} scene, and nothing in Sources uses SettingsLink. The live cap, auto mode, accounts, GitHub polling, and repo roots live in config.json and sb flags. Issue sources are a sheet on the Issues view.

Why it matters

Every Mac app has an app menu item named Settings… with ⌘,. Users look there first, and right now they have to find config.json or the sb docs instead.

Suggested fix

Add a Settings scene with tabs:

  • General: the live cap, auto mode, and the default account.
  • Issues: move IssueSetupView here.
  • Advanced: a button that opens config.json.

Write changes through sbd so config.json stays the source of truth.

This is finding 10 of the #295 UI once-over. Open PRs #376, #383, and #260 change App.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.