I recently noticed the new API documentation (looks very nice, btw) and observed that a lot of fields previously marked "some-type or null" in the old documentation no longer have the "or null" specified. However, API requests still supply null values where the new documentation does not specify that they will be there. I suspect there is some statement about nulls that I may have missed. Can someone provide a link, reference or statement that I can use as a guide in my app on where TMDB might supply null values unexpectedly or how I can know when to expect null values. That would be much appreciated.
映画やテレビ番組が見つかりませんか?ログインして作成してください。
このアイテムを評価したり、リストに追加したりしたいですか?
メンバーではありませんか?
pajatopmrからの返信
投稿:2023年07月06日 7:42 AM
After doing some searching, I now believe the current documentation is the old documentation with a new face that does not indicate where nulls are relevant. Love to hear that I'm wrong.
Visneからの返信
投稿:2024年02月09日 9:27 PM
I think you are correct, and this is quite sad.
rednazからの返信
投稿:2024年06月24日 6:44 AM
I've stumbled across this recently when trying to get some robustness around the API. It's hard to write defensive code when you aren't sure what can be null. Surely the only option isn't to just assume everything can be null?
Travis Bellからの返信
投稿:2024年06月25日 2:08 PM
Our hands are unfortunately tied until ReadMe (our docs provider) adds supports this. At this time, I am not able to change it because it's not supported.
AlexanderYTaylorからの返信
投稿:2025年02月14日 7:44 PM
Travis is this able to be updated yet?
It would be great to know what fields might be returned as null
Travis Bellからの返信
投稿:2025年02月14日 10:01 PM
As far as I know nothing has changed with ReadMe yet.