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.
Nu găsiți un film sau un serial? Autentificați-vă pentru a-l crea.
Doriți să evaluați sau să adăugați acest element într-o listă?
Nu eşti membru?
Răspuns de pajatopmr
pe data de 6 iulie 2023 la ora 7:42AM
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.
Răspuns de Visne
pe data de 9 februarie 2024 la ora 9:27PM
I think you are correct, and this is quite sad.
Răspuns de rednaz
pe data de 24 iunie 2024 la ora 6:44AM
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?
Răspuns de Travis Bell
pe data de 25 iunie 2024 la ora 2:08PM
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.