[Bug]: Desktop: Title page download summary shows zero counts and a trailing separator

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

The summary line is built at desktop/app/src/browsing/view/title.rs:445; read that function and the surrounding view code to see how each counter and the profile name are appended. Compare against the web's SeriesPanel component to copy its rules for hiding zero counts, colouring, and joining with a separator. Reproduce with cargo run --locked -- --scene title --snapshot /tmp/t.png from desktop/ and re-run it to confirm the trailing " · " is gone and only non-zero parts remain.

Written by the indexing model from the issue text.

Description

bug

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a review session of the desktop app (#80) with @PhrolovaMoe. It was found in headless renders of the debug build's fixture scenes (--snapshot), not on a live server.

Version

0.40.0 (feat/desktop, 017a837b)

Area

Other (desktop app)

What happened?

The managed show summary on the title page (desktop/app/src/browsing/view/title.rs:445) prints every counter, even zeros ("0 downloading · 0 missing · 0 skipped"), then the profile name. When the profile name is empty the line ends with a stray " · ". The web's SeriesPanel only shows non-zero counts, colours downloading/to find/missing, and adds the next schedule time.

Steps to reproduce

From desktop/, with a debug build: cargo run --locked -- --scene title --snapshot /tmp/t.png: the line ends in "0 skipped ·".

Expected behavior

The same summary as the web.

Suggested fix

Build the line from only the non-zero parts (with the web's colours), join them with " · ", and skip empty values.

Dominant language
TypeScript
Stars
4
Forks
1
Avg merge
4h 49m
Merged PRs (30d)
5

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 tinystream-dev/tinystream

All issues in tinystream-dev/tinystream

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.