You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I build Sportarr (https://github.com/Sportarr/Sportarr), a sports event manager that speaks the Sonarr v3 contract (leagues surface as series, events as episodes). People already point Seerr at it through that compatibility, and I'd like it to be a first-class server type instead. I've built and validated a working implementation on a branch (a SportarrAPI extending SonarrAPI the way Whisparr rides Radarr across the ecosystem, its own settings section and modal, full test suite and production build passing, verified end to end against a live instance). Before opening a PR I want to ask whether that's something you'd accept and how you'd want it shaped. One design point worth your input up front: discovery is TMDB-keyed today, so sports requests only work where a league maps to a browsable entry; first-class sports discovery backed by Sportarr's public metadata API feels like a natural phase 2 but needs your direction. Happy to adapt the work to whatever structure you prefer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi. I build Sportarr (https://github.com/Sportarr/Sportarr), a sports event manager that speaks the Sonarr v3 contract (leagues surface as series, events as episodes). People already point Seerr at it through that compatibility, and I'd like it to be a first-class server type instead. I've built and validated a working implementation on a branch (a SportarrAPI extending SonarrAPI the way Whisparr rides Radarr across the ecosystem, its own settings section and modal, full test suite and production build passing, verified end to end against a live instance). Before opening a PR I want to ask whether that's something you'd accept and how you'd want it shaped. One design point worth your input up front: discovery is TMDB-keyed today, so sports requests only work where a league maps to a browsable entry; first-class sports discovery backed by Sportarr's public metadata API feels like a natural phase 2 but needs your direction. Happy to adapt the work to whatever structure you prefer.
All reactions