You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The spotify API returns "null" as part of the "items" for some Podcasts (for example Lateral by Tom Scott). The response JSON looks like this:
Notice that using Option<SimpliefiedEpisode> fixes this.
Expected behavior
I expect all episodes to be loaded properly.
Log/Output data
Serde is not able to parse the json.
Additional context
I use spotify_player for music playback and have long been plagued by some podcasts not loading. Now that I have examps coming up, it's the perfect time to procrastinate on open source lol
The text was updated successfully, but these errors were encountered:
It seems that Spotify has changed the behavior of their APIs again, I've encountered this problem more times than I can count. Originally, the API returned a SimplifiedEpisode. If an episode was null, it would skip it and return nothing.
To address this issue, I have an idea: instead of directly updating the return type from SimplifiedEpisode to Option<SimplifiedEpisode>, I prefer to introduce a wire version that is flexible and adaptable to any changes Spotify makes. This approach allows us to continue using SimplifiedEpisode as the facade version without introducing breaking changes for library users.
Describe the bug
The spotify API returns "null" as part of the "items" for some Podcasts (for example Lateral by Tom Scott). The response JSON looks like this:
To Reproduce
Steps to reproduce the behavior:
cargo run
Option<SimpliefiedEpisode>
fixes this.Expected behavior
I expect all episodes to be loaded properly.
Log/Output data
Serde is not able to parse the json.
Additional context
I use spotify_player for music playback and have long been plagued by some podcasts not loading. Now that I have examps coming up, it's the perfect time to procrastinate on open source lol
The text was updated successfully, but these errors were encountered: