Show subtitle state on title detail #201
No Assignees
Notifications
Due Date
No due date set.
Reference: yolo/arr#201
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Show subtitle state on the title detail surface (§9.6) — the answer to "does
this have Portuguese, and where did it come from".
Per media file, one row of chips: each language present, its origin (embedded,
extracted, the provider name, or the engine that translated it), forced or SDH
where applicable, and whether
alasssynced it or its sync was rejected. Amachine translation reads as machine-made at a glance; that is the whole point
of tracking origin.
A language that is wanted and missing shows as missing, with the reason from
the attempt row — searching, no candidates, waiting on budget, translation
failed. Not an empty space.
This is
area/web: go through theimpeccableskill before writing markup,per
CLAUDE.md. Chips and fixed structure, no horizontal scroll, consistentwith the release deck.
Depends on: #199
Implemented per §9.6/§15: a subtitle-status chip row on both the movie and series detail pages, one row per media file. Present languages get a chip carrying origin (embedded/extracted/provider name/translated engine), SDH, forced and a "sync flagged" marker for a rejected
alassrun; a machine translation carries a dashed border in addition to theMTtext marker so it reads as machine-made at a glance without hovering. A wanted-but-missing language gets its own amber chip naming why —searching,no candidates,capped, orfailedwith the last-failure detail (truncated, full text in the tooltip).Backend: added
GET /api/movies/{id}/subtitles/status,GET /api/episodes/{id}/subtitles/status, and a bulkGET /api/series/{id}/subtitles/status(mirroringseries::files's join, so the series detail page costs one call rather than one per episode). Satisfaction is computed fromsubtitle_files, never fromsubtitle_attempts.state, per §15's explicit rule that the attempt row must never become a second source of truth. A missing language with no attempt row yet (the reconcile loop hasn't reached it — #196 isn't wired in yet) reads the same assearching.Frontend: new
web/src/subtitles.tsdata module (interfaces + fetch functions + label formatting), wired intomovieMain/seriesMaininmain.ts, styled with the existing token system — reused the release deck'sdata-verdict="eligible"green and the library'sdata-movie-state="missing"amber ramps rather than inventing new colours, plus one new.chip[data-mt="true"]dashed-border rule. Went through theimpeccableskill; the detector found nothing. Verified live withagent-browseragainst a seeded dev database (desktop + 390px mobile — wraps cleanly, no horizontal scroll) for both the movie and the series/episode surfaces.Branch:
subtitles/201-title-subs-ui(pushed).just ci: passed (658 tests, clippy, fmt, machete, biome, tsc, check-tokens all green).Findings
blitz/subtitlesyet — nothing currently callsarr_db::subtitles::want(), sosubtitle_attemptsrows only exist for languages a manual grab/translate/search has already touched. This UI is correct either way (falls back tosearchingfor an untouched wanted language), but until #196 lands, most real files will show missing chips assearchingeven when nothing has actually searched yet — worth knowing when reviewing screenshots against a live library.arr_db::NewSubtitleFile::embedded/::extractedare only ever constructed inarr-api's own tests. Out of scope here, but the "embedded" and "extracted" origin chips this issue asks for won't have real data until that lands.