Open glensc opened 2 years ago
Perhaps instead of adding episodes
property, replace the implementation with seasons
property?
but then it would be a breaking change due list
vs dict
.
Note that the current data is all fetched and filled by TVShow
only (no extra requests), not in TVSeason
, TVEpisode
individually, so the old code needs to remain for the TVSeason
or TVEpisode
direct creation to continue working.
or rename new property to season_episodes
?
perhaps the list
vs dict
is not an issue since accessing season from list
by index is unreliable anyway (season 0 aka extras may be present and may be missing). however the same does not apply for episodes, in list episode 1 is episodes[0]
not episodes[1]
.
I've given this a thought, perhaps:
I've also started abstracting HTTP and API layer:
so, if someone wants to make raw queries without the abstraction of the object they can use just the API client class. reasons could be any of:
Ok. I've removed changes making this incompatible for v3
Incompatible changes moved to separate PR for v4:
This will make only one trakt.tv API request to create list of
TVSeason
withTVEpisode
objects.The properties are indexed in a(moved to https://github.com/moogar0880/PyTrakt/pull/185)dict
by.number
rather being alist
.this will make only two requests:
This is a continued effort to replace internal implementation: