We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While my previous approach was to trust the API values apparently they keep causing issues.
Hence it would be a sane approach to check the API return values for null, emptystring etc. before assigning/processing them.
Particularly tmdb poster paths apparently can be null which just causes a coredump...
To prevent this from happening we should sanity check everything according to the relevant API definitions (i.e. if a field can return null or not).
The text was updated successfully, but these errors were encountered:
CptPie
No branches or pull requests
While my previous approach was to trust the API values apparently they keep causing issues.
Hence it would be a sane approach to check the API return values for null, emptystring etc. before assigning/processing them.
Particularly tmdb poster paths apparently can be null which just causes a coredump...
To prevent this from happening we should sanity check everything according to the relevant API definitions (i.e. if a field can return null or not).
The text was updated successfully, but these errors were encountered: