feat(web): search titles and pick a release #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/search-screen"
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?
Phase 7, step 4: the Search screen of the mockup.
What it does
search.svelte.ts, like the Magnet screen's, so it survives a trip to another tab.GET /api/catalog/searchresults, one group per catalog title: title,year · Movie|Show|Anime, original title (muted) when different, release count once loaded (3 of 5 releaseswhen filters hide some). No posters, as in the mockup. The first group opens after a search.GET /api/releases. Opening a show loads its details first and shows season chips (S1,S2…, specials hidden); season 1 is picked by default (the start of the show), and picking another loads that season.kind:id:seasonin the browser until the next search (a new search asks the indexers again, seeders change). A failed load is asked again on reopen.quality/pack(resolution, DV, HDR, x265/AV1, languages,S02/S01–S03/Batchfor anime,Completefor shows), SRC (indexer ids from the answer), SIZE, SEED (accent ≥ 100, warning below,–when unknown), LEECH, Select. Skeleton rows while loading, empty states.failedare listed in one discreet line under the table, the error on hover. Catalogerrors(a source down) show as a small warning alert.N titles · M releases.from searchbadge and fetches the metadata. The releases answer'stargetreplaces theproposalguessed from the name (still editable). Pasting a magnet works as before (no badge, guessed target); typing in the field drops the badge.No Rust change.
Checks
npm ci && npm run check && npm run build: 0 errors, 0 warnings.🤖 Generated with Claude Code
0b8e06872b1a98790449