Skip to content

Spotify api update#162

Open
easotelo1 wants to merge 4 commits intosigma67:mainfrom
easotelo1:spotify-api-update
Open

Spotify api update#162
easotelo1 wants to merge 4 commits intosigma67:mainfrom
easotelo1:spotify-api-update

Conversation

@easotelo1
Copy link

@easotelo1 easotelo1 commented Feb 21, 2026

  • Copying public playlists to youtube is no longer allowed with the recent api changes. Only USER playlists is possible
    • Updated tests to account for this
  • getPlaylist(playlistId) response has changed. Updated keys to reflect response changes
    • getLikedPlaylist() and getPlaylist() also have differing responses now. Updated build_results to account for this
  • Added mocked test data to update unit tests that were now failing due to spotify api changes
  • Updated all tests to reflect changes
  • Updated readme

@easotelo1 easotelo1 marked this pull request as draft February 21, 2026 02:32
@easotelo1 easotelo1 marked this pull request as ready for review February 21, 2026 02:43
@easotelo1
Copy link
Author

easotelo1 commented Feb 21, 2026

@sigma67 I'm not entirely sure if i'm missing anything else but it seems like the code coverage is failing from some of the very same tests that i updated. For example,

tests/test_spotipy.py::TestSpotify::test_getUserPlaylists FAILED [100%]

This test no longer exists from my changes.

I could be wrong here but it seems like it's having issues doing a token refresh from the secrets.SETTINGS_INI.

Finally, the folks over at Spotipy are also working on updating their api calls. In order to get the unit tests to work on my end, I had to edit the spotipy installed package library manually. I would assume that the code coverage would continue to fail until Spotipy new version releases with the updated API changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants