status line: a summary of all sessions (connected, reconnecting, forwards)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The payload names no files, so begin with the status line that currently describes only the active tab, and with the per-session connection state that the toast for a dropped session is raised from. Work out how to read the state of every open session, not just the active one. Done means the status line shows counts such as connected, reconnecting and forwards across all sessions, and clicking one count switches to the matching tab. The payload leaves the exact format and click target open, so confirm the design with a maintainer before coding.
Written by the indexing model from the issue text.
Description
What would you like to be added?
A short summary at the right end of the status line covering every open session, not only the active one. For example 3 connected · 1 reconnecting · 2 forwards. Clicking a part jumps to the matching tab, such as the session that is reconnecting.
Why is this needed?
Today the status line describes only the active tab, so a session that dropped in another tab is only visible as a toast that disappears. Shipyard's bottom bar (1 needs you · 2 working · queued (3)) shows how much a one-line summary helps when several things run at once.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 2
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 36
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 your-moon/tern
-
area::tern kind::feature triage::needs-decision
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
area::tern kind::feature triage::needs-decision
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
area::tern kind::feature triage::needs-decision
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
area::tern kind::bug triage::ready
Difficulty 3/5 Half a day Newbie friendliness 62/100
your-moon/tern#64 · 1 comment ·
Maintainers usually reply within 1 day
-
epic::1.0 plan
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
area: compat area: parsing bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reubeno/brush#1526 · 1 comment ·
Maintainers usually reply within 1 day
-
OFN writer emits `DocIRI` as a bare IRI, which becomes a version IRI or a parse error on re-readOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
phillord/horned-owl#338 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stackabletech/operator-rs#1301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jmcnamara/rust_xlsxwriter#205 · 4 comments ·