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
Describe the solution you'd like
I would like the with_release_type attribute to be added to tmdb_discover so I can filter matches based whether or not a movie had a specific type of release.
It would be nice to filter results based on release type. 1 = Premiere 2 = Theatrical (limited) 3 = Theatrical 4 = Digital 5 = Physical 6 = TV
Additional info
What would BEST suit my needs, would actually be a without_release_type. However, that doesn't seem to be supported by the TMDb API, and I think to do it ourselves would require calling the GET movie release dates endpoint for each match, which seems like a bad idea. If you can think of a way around this limitation I'd greatly appreciate it, but I didn't make it officially part of this request because it seems out of scope, and perhaps separate ticket.
I am of course willing to help and create Pull Requests if you'd like.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The recent update to the TMDb Discover attributes added support for the
with_type
Discover TV attribute, but did not add the equivalentwith_release_type
Discover Movie attribute.Describe the solution you'd like
I would like the
with_release_type
attribute to be added to tmdb_discover so I can filter matches based whether or not a movie had a specific type of release.It would be nice to filter results based on release type.
1
= Premiere2
= Theatrical (limited)3
= Theatrical4
= Digital5
= Physical6
= TVAdditional info
What would BEST suit my needs, would actually be a
without_release_type
. However, that doesn't seem to be supported by the TMDb API, and I think to do it ourselves would require calling the GET movie release dates endpoint for each match, which seems like a bad idea. If you can think of a way around this limitation I'd greatly appreciate it, but I didn't make it officially part of this request because it seems out of scope, and perhaps separate ticket.I am of course willing to help and create Pull Requests if you'd like.
The text was updated successfully, but these errors were encountered: