Say who the tray is signed in as, and against which endpoint #3
No reviewers
Labels
No labels
⏳in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grey.ooo/someones.computer_tray!3
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/signed-in-as"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #578. Needs scclient #3 and the platform's #628.
The menu could show a whole tree of applications without ever saying whose they were — a real gap in something set up once and glanced at for months, whose token comes from a file or an environment variable, and where a tray on staging looks exactly like one on production.
The row names the person, the token when the platform named one, and the endpoint. Asked once at startup, not on the poll: an identity does not change under a running tray, and re-asking every ten seconds would be six requests a minute to re-learn the same name. An unreachable platform falls back to the endpoint alone — the sync right after is where "the platform is down" gets said properly.
Per the capture policy, the stub scene answers
/cli/metoo, so the row is in the screenshots rather than only in a test. The stub now serves onsomeones.localhostrather than a loopback address, because this row prints the endpoint andhttp://127.0.0.1:8099in a manual reads like a mistake.go build,go vet,go test ./...clean; captures regenerated for all three themes.WIP: Say who the tray is signed in as, and against which endpointto Say who the tray is signed in as, and against which endpoint