fix: handle missing 'popularity' field in Spotify API response (issue #36)#39
Closed
vanhci wants to merge 1 commit into
Closed
fix: handle missing 'popularity' field in Spotify API response (issue #36)#39vanhci wants to merge 1 commit into
vanhci wants to merge 1 commit into
Conversation
…36) The Spotify API deprecated the 'popularity' field in track responses. This caused a KeyError when trying to access track['item']['popularity']. Use .get() to safely handle missing field, defaulting to -1.
Member
|
Duplicate of #37 which was just merged |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #36
The Spotify API has deprecated the
popularityfield in track responses. When this field is missing from the API response, accessingtrack["item"]["popularity"]raises aKeyError: 'popularity'.Changes
.get("popularity")instead of direct dict access to safely handle the missing field-1when the field is absent (preserving the existing fallback behavior)Testing
This is a runtime fix for a Spotify API deprecation. The field was already removed from newer API responses. The fix ensures backward compatibility with both old and new API responses.