Skip to content
New issue

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

Updated specific result/response interface fields from null to current appropriate type #28

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
updated formatting, and changed the changeset to include more info
justmeeos committed Mar 8, 2024
commit 28a465b3c5f59a44a16c8f146ded721728792ec9
16 changes: 8 additions & 8 deletions .changeset/warm-toys-buy.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
"tmdb-js-core": patch
---
Summary:
Large number of result and response data types had fields like poster_path and backdrop_path changed from a "null" data type to "null | string" data type. To
accurately reflect the data type the api can return

What:
Modified a large number of the api result interfaces to change fields that were typed as null to fields with their correct type. This is frequently null | string
Why:
The api can return a null value for those specific fileds, but it can also return a string value as well, so this update reflects the current state of tmdb api

Summary:
Large number of result and response data types had fields like poster_path and backdrop_path changed from a "null" data type to "null | string" data type. To
accurately reflect the data type the api can return.

What:
Modified a large number of the api result interfaces to change fields that were typed as null to fields with their correct type. This is frequently null | string
I don't think there was another data type other than null | string needed, but if there was I had checked it against the api documentation so it should be correct
Why:
The api can return a null value for those specific fileds, but it can also return a string value as well, so this update reflects the current state of tmdb api
Loading