[PR #133] [MERGED] Fix playlist related endpoints #262

New issue

Closed

opened 2026-02-27 20:24:00 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:24:00 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/ramsayleung/rspotify/pull/133
Author: @ghost
Created: 10/8/2020
Status: ✅ Merged
Merged: 10/24/2020
Merged by: @ramsayleung

Base: master ← Head: fix_playlist_api

📝 Commits (10+)

292c082 Fix get-playlists-tracks endpoint
fcbecb5 Fix change-playlist-details endpoint
3a9e6c5 Fix unfollow-playlist endpoint
55b16a0 Fix add-tracks-to-playlist endpoint
73b7d2f Fix replace-playlists-tracks endpoint
82d2006 Fix reorder-playlists-tracks endpoint
87abd82 Fix remove-tracks-playlist endpoint
3c5cb7b Fix remove-tracks-playlist endpoint
3201233 Fix follow-playlist endpoint
1419d25 Fix check-user-following-playlist endpoint

📊 Changes

2 files changed (+40 additions, -90 deletions)

View changed files

📝 src/client.rs (+20 -46)
📝 tests/test_with_oauth.rs (+20 -44)

📄 Description

Most of the API for handling playlists required a user ID in addition to the playlist ID. However, the Spotify API only requires the playlist ID for its endpoints, see here.

I suppose that in a previous version of the Spotify API, the owner ID was needed to correctly identify a playlist, but it seems to no longer be the case.

This PR fixes the calls to the playlist related actions, and renames the methods of the client for more clarity.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/ramsayleung/rspotify/pull/133 **Author:** [@ghost](https://github.com/ghost) **Created:** 10/8/2020 **Status:** ✅ Merged **Merged:** 10/24/2020 **Merged by:** [@ramsayleung](https://github.com/ramsayleung) **Base:** `master` ← **Head:** `fix_playlist_api` --- ### 📝 Commits (10+) - [`292c082`](https://github.com/ramsayleung/rspotify/commit/292c08209dfbc8a0d77c8b679990e148415841fa) Fix get-playlists-tracks endpoint - [`fcbecb5`](https://github.com/ramsayleung/rspotify/commit/fcbecb531268fd98a49d696c86ecb9585a1b310a) Fix change-playlist-details endpoint - [`3a9e6c5`](https://github.com/ramsayleung/rspotify/commit/3a9e6c54812360e9beb9b861a0ab74cdc87c65fd) Fix unfollow-playlist endpoint - [`55b16a0`](https://github.com/ramsayleung/rspotify/commit/55b16a0ec83ae1ae8e42c5a5f3981cc8e941b1bf) Fix add-tracks-to-playlist endpoint - [`73b7d2f`](https://github.com/ramsayleung/rspotify/commit/73b7d2f329d5e41c189a3b3c3cd8097a64dea7df) Fix replace-playlists-tracks endpoint - [`82d2006`](https://github.com/ramsayleung/rspotify/commit/82d2006eff9c5e30edbcdbf02b6bf70400802eae) Fix reorder-playlists-tracks endpoint - [`87abd82`](https://github.com/ramsayleung/rspotify/commit/87abd82e9add038221a199ca1bf1ed7c1970116d) Fix remove-tracks-playlist endpoint - [`3c5cb7b`](https://github.com/ramsayleung/rspotify/commit/3c5cb7b256795d1561d7daa6cbc02e58fe942e30) Fix remove-tracks-playlist endpoint - [`3201233`](https://github.com/ramsayleung/rspotify/commit/3201233c516bc1a78de4b98c77566a1afbf58abc) Fix follow-playlist endpoint - [`1419d25`](https://github.com/ramsayleung/rspotify/commit/1419d2524d5621954f0ae042b3a4e2b720e65901) Fix check-user-following-playlist endpoint ### 📊 Changes **2 files changed** (+40 additions, -90 deletions) <details> <summary>View changed files</summary> 📝 `src/client.rs` (+20 -46) 📝 `tests/test_with_oauth.rs` (+20 -44) </details> ### 📄 Description Most of the API for handling playlists required a user ID in addition to the playlist ID. However, the Spotify API only requires the playlist ID for its endpoints, [see here](https://developer.spotify.com/documentation/web-api/reference/playlists/). I suppose that in a previous version of the Spotify API, the owner ID was needed to correctly identify a playlist, but it seems to no longer be the case. This PR fixes the calls to the playlist related actions, and renames the methods of the client for more clarity. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>