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.
Fılmdi nemese kórsetimdi taba almadyńyz ba? Ony jasaý úshin kirińiz.
Want to rate or add this item to a list?
Not a member?
pajatopmr jaýaby
2023 Shilde 6 kúni 7:42 AM ýaqytynda
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 jaýaby
2024 Aqpan 9 kúni 9:27 PM ýaqytynda
I think you are correct, and this is quite sad.
rednaz jaýaby
2024 Maýsym 24 kúni 6:44 AM ýaqytynda
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 jaýaby
2024 Maýsym 25 kúni 2:08 PM ýaqytynda
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 jaýaby
2025 Aqpan 14 kúni 7:44 PM ýaqytynda
Travis is this able to be updated yet?
It would be great to know what fields might be returned as null
Travis Bell jaýaby
2025 Aqpan 14 kúni 10:01 PM ýaqytynda
As far as I know nothing has changed with ReadMe yet.