I'm pretty sure they are neither. But is it necessary to do that?
If so, we'll have to make a workaround which creates the object if it's not there and fills in blanks, so that the end user will get the same experience every time they call the API (can't have stuff being null if you explicitly asked for it).
You don't need to have done any of the account actions on the item (rated, watchlist or favorite) but you do need a valid session_id for the account_sates field to show up.
I can call any arbitrary item and get back you'd expect:
LordMike 的回复
于 2015 年 06 月 18 日 4:48下午
For the record, when implementing TvEpisode and TvSeason, I couldn't append Account_states either.
Travis Bell 的回复
于 2015 年 06 月 19 日 10:47上午
Hi guys,
I've created a new ticket for this here. I'll look at it next week.
Travis Bell 的回复
于 2015 年 06 月 19 日 6:15下午
Hmm, all of my tests for series, seasons and episodes are working with one of my sessions:
Request:
Response
Request
Response
Request
Response
Are you sure you're calling the methods with a session that has rated or marked one of the items (as a favourite or watch list)?
LordMike 的回复
于 2015 年 06 月 20 日 6:30上午
I'm pretty sure they are neither. But is it necessary to do that?
If so, we'll have to make a workaround which creates the object if it's not there and fills in blanks, so that the end user will get the same experience every time they call the API (can't have stuff being null if you explicitly asked for it).
Travis Bell 的回复
于 2015 年 06 月 20 日 10:15上午
You don't need to have done any of the account actions on the item (rated, watchlist or favorite) but you do need a valid
session_id
for theaccount_sates
field to show up.I can call any arbitrary item and get back you'd expect:
LordMike 的回复
于 2015 年 06 月 20 日 10:27上午
Oooh.. Might be we missed the session id.. Makes sense.