Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any Chance of adding v4 list support? #263

Open
devbrian opened this issue Apr 12, 2018 · 5 comments
Open

Any Chance of adding v4 list support? #263

devbrian opened this issue Apr 12, 2018 · 5 comments

Comments

@devbrian
Copy link

Would love v4 list support, as you can add many movies to a list at a time.

https://developers.themoviedb.org/4/list/update-items

@LordMike
Copy link
Collaborator

.. I suppose we should get started on the V4 client.

@wwarby
Copy link

wwarby commented Jan 27, 2021

Any update on this? I could be up for contributing as I'd like to start using v4 lists in my own project.

@LordMike
Copy link
Collaborator

You could try - I think partly the issue was putting the flexibility of the api into C# objects ..

I suppose one way of handling these very flexible things, would be "features".. Ie, a response object with a "TryGetFeature(out Actors actors)"..

Let me know what you think of the v4 api and how it could be tackled.

@wwarby
Copy link

wwarby commented Apr 24, 2022

I put this aside for a while due to other priorities but I'm gonna need to start using these APIs soon, so I need to either add support for this stuff in TMDbLib or use RestSharp for the features I need, which I'm not especially keen on. Specifically what I'm looking for in my project is to retrieve my rated and watchlisted movies and TV shows.

I've been looking at the API docs this morning and I'm not sure I've understood what you're referring to with regards to the flexibility in the API. I see one endpoint which is somewhat problematic - Get List, which returns an array of results that can be one of two types - a TV List Results object or a Movie List Results object. I suppose there's a few different ways to tackle that which would need an agreed approach, but the rest of the API looks pretty straightforward to me. Can you explain where in the API you see the flexibility that is problematic? or is it just that one endpoint...

@wwarby
Copy link

wwarby commented Apr 24, 2022

I've just had a closer look at the documentation and it seems everything I need is actually available in the v3 API - don't know why I didn't notice that before, so I'm gonna stick with that for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants