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.
찾으시는 영화나 TV 프로그램이 없나요? 로그인 하셔서 직접 만들어주세요.
Want to rate or add this item to a list?
Not a member?
pajatopmr님의 댓글
7월 6, 2023 at 7:42 오전
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님의 댓글
2월 9, 2024 at 9:27 오후
I think you are correct, and this is quite sad.
rednaz님의 댓글
6월 24, 2024 at 6:44 오전
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님의 댓글
6월 25, 2024 at 2:08 오후
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.