Trailer resolution endpoint keyed on a TMDB id #144
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: yolo/arr#144
Reference in New Issue
Block a user
Depends on: #143
§9.6 resolves a trailer on click rather than up front, because TMDB's search
responses carry no videos and prefetching one detail call per rendered row
would put ~20 requests behind a search-as-you-type box.
That needs an endpoint keyed on a TMDB id, not a local id — the chip appears
on TMDB rows for titles that are not in the library and have no local row to
address.
movie_videos/series_videosfrom #143, so the selection rule livesin one place and this handler does not re-implement it.
anyone, costs nothing upstream.
tmdb_client()pathin
arr-api/src/search.rs— 503, same error body shape.outcome and the browser renders it as "no trailer", so it must be
distinguishable from an upstream failure.
Annotate for OpenAPI like the handlers around it.
Do not start until
blitz/tv-trackingis on main — it rewritesarr-api/src/search.rs, which this sits next to.