459b8ab730176375c2cac55d628e851de6704e3b
Verified against live ReClip: POST /api/download with title:"" → a hash filename (b5d04adc86.mp3); with title:"Me at the zoo" → "Me at the zoo.mp3". So ReClip names the file from the title WE send (falling back to a hash) — it does not self-name. The title is mandatory, which means a metadata pass is required. Back to two phases: 1. metadata — fetch each item's /api/info (title + validity), keep survivors, skip errors. 2. download — download each survivor passing its title, so files land with real names; skip download errors. Keeps the exact-urls[] input (Mix playlists can't drift) and the one-request-per- item download. Progress is two counters again (Titles + Download); UI shows two bars. ~2 requests/item is inherent to needing the title (per the user's call: correctness over speed). Verified two-phase filtering + title passthrough + skip-on-error with a mock. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%