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.
Bir filmi veya diziyi bulamıyor musun? Eklemek için oturum aç.
Bu öğeyi derecelendirmek veya bir listeye eklemek ister misiniz?
Üye değil misin?
Yanıtla pajatopmr
J 6, 2023 tarihinde saat 7:42 ÖÖ'da
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.
Yanıtla Visne
i 9, 2024 tarihinde saat 9:27 ÖS'da
I think you are correct, and this is quite sad.
Yanıtla rednaz
" 24, 2024 tarihinde saat 6:44 ÖÖ'da
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?
Yanıtla Travis Bell
" 25, 2024 tarihinde saat 2:08 ÖS'da
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.