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

arr-core domain types #7

New Issue
Closed
opened 2026-08-22 18:22:38 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-22 18:22:38 +01:00
Owner
Copy Link
Copy Source

The types in DESIGN.md §4, movies only. No IO, no sqlx, no axum — this crate
must stay dependency-light (CLAUDE.md, the invariant).

Model the things that are easy to get subtly wrong:

  • Language distinguishing pt-PT, pt-BR and por-unverified (§5.2).
  • HdrFormat with the DV profile as data, not a boolean (§5.3).
  • Verdict as Eligible | Waived(rule) | Rejected(rule), so a rejection always
    carries which rule killed it (§9.3).
  • Intent as wanted on the leaf, never a monitored flag (§4.1).

Acceptance: the crate compiles with no reqwest, sqlx or axum in its
dependency tree, and cargo tree proves it.

Depends on: #1

Labels: phase/2-logic, area/core, difficulty/moderate, type/feature

The types in `DESIGN.md` §4, movies only. No IO, no sqlx, no axum — this crate must stay dependency-light (`CLAUDE.md`, the invariant). Model the things that are easy to get subtly wrong: - `Language` distinguishing `pt-PT`, `pt-BR` and `por-unverified` (§5.2). - `HdrFormat` with the DV profile as data, not a boolean (§5.3). - `Verdict` as `Eligible | Waived(rule) | Rejected(rule)`, so a rejection always carries which rule killed it (§9.3). - Intent as `wanted` on the leaf, never a `monitored` flag (§4.1). Acceptance: the crate compiles with no `reqwest`, `sqlx` or `axum` in its dependency tree, and `cargo tree` proves it. --- **Depends on:** #1 Labels: `phase/2-logic`, `area/core`, `difficulty/moderate`, `type/feature`
naps62-yolo added the phase/2-logicarea/coredifficulty/moderatetype/feature labels 2026-08-22 18:22:38 +01:00
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/core difficulty/moderate phase/2-logic 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#7
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?