yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Series API and UI #39

New Issue
Closed
opened 2026-08-22 18:22:40 +01:00 by naps62-yolo · 1 comment
naps62-yolo commented 2026-08-22 18:22:40 +01:00
Owner
Copy Link
Copy Source

Series equivalents of the movie endpoints, plus season and episode granularity:
set auto_track, mark individual seasons or episodes wanted, per-episode manual
search.

UI reuses the components from phase 5 — buckets, chips, derived status. If they
need forking rather than reusing, say so on the issue; that is a signal the
phase 5 components were built too narrowly.

Depends on: #34, #29, #36

Labels: phase/6-tv, area/api, difficulty/moderate, type/feature

Series equivalents of the movie endpoints, plus season and episode granularity: set `auto_track`, mark individual seasons or episodes wanted, per-episode manual search. UI reuses the components from phase 5 — buckets, chips, derived status. If they need forking rather than reusing, say so on the issue; that is a signal the phase 5 components were built too narrowly. --- **Depends on:** #34, #29, #36 Labels: `phase/6-tv`, `area/api`, `difficulty/moderate`, `type/feature`
naps62-yolo added the area/apiphase/6-tvdifficulty/moderatetype/feature labels 2026-08-22 18:22:40 +01:00
naps62-yolo commented 2026-08-22 22:53:04 +01:00
Author
Owner
Copy Link
Copy Source

The API half is in #81. The UI half is not, and the reason is the one this
issue asks about.

The issue says the UI reuses the phase 5 components — buckets, chips, derived
status. Those are #31, #32 and #33, all still open; #31 has a PR in flight
(#79) and the other two have not started. So it is not that the components are
too narrow to reuse — they do not exist on main yet. Building series views
now would mean writing the bucket table, the chip set and the status treatment
here, which is three other issues implemented inline.

Series views should follow once #31, #32 and #33 land, and at that point the
reuse-versus-fork question this issue raises can actually be answered.

Two API-side notes worth carrying forward:

  • The series table has no TVDB ID, so an episode search cannot use
    t=tvsearch&tvdbid= and falls back to a text search with the SxxEyy tag.
    That fallback is what DESIGN.md §6.1 describes, but ID-based TV search stays
    unavailable until TV metadata refresh exists to populate one. There is no
    issue for TV metadata refresh yet.
  • GET /api/releases?episode_id= returns 422 when the series has no
    original_language, rather than guessing one. §5.2 writes the language rule
    against the title's original language, so a guess would silently change every
    verdict.
The API half is in #81. The UI half is not, and the reason is the one this issue asks about. The issue says the UI reuses the phase 5 components — buckets, chips, derived status. Those are #31, #32 and #33, all still open; #31 has a PR in flight (#79) and the other two have not started. So it is not that the components are too narrow to reuse — they do not exist on `main` yet. Building series views now would mean writing the bucket table, the chip set and the status treatment here, which is three other issues implemented inline. Series views should follow once #31, #32 and #33 land, and at that point the reuse-versus-fork question this issue raises can actually be answered. Two API-side notes worth carrying forward: - The series table has no TVDB ID, so an episode search cannot use `t=tvsearch&tvdbid=` and falls back to a text search with the `SxxEyy` tag. That fallback is what DESIGN.md §6.1 describes, but ID-based TV search stays unavailable until TV metadata refresh exists to populate one. There is no issue for TV metadata refresh yet. - `GET /api/releases?episode_id=` returns 422 when the series has no `original_language`, rather than guessing one. §5.2 writes the language rule against the title's original language, so a guess would silently change every verdict.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/api difficulty/moderate phase/6-tv type/feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#39
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?