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

Improve documentation on handling local tracks #886

Open
nitricware opened this Issue May 20, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@nitricware
Copy link

nitricware commented May 20, 2018

Issue found on May 20, 2018

Endpoint(s):

  • DELETE /v1/users/{user_id}/playlists/{playlist_id}/tracks

Scope(s):

  • playlist-modify-public playlist-modify-private

Steps to reproduce:

(Since this issue is about the documentation...)

  1. Check documentation
  2. Try to find information on handling local tracks

Expected behaviour:

A clear documentation on handling local tracks with examples.

Actual behaviour:

A very genereal support document (https://developer.spotify.com/web-api/local-files-spotify-playlists/) Which is talking about indexes (which can't be found anywhere else) rather than positions (which may not even be the same).

I am also referring to this issue: #612 (Also, a clarification on what the request body must look like to work with local tracks in the issue tracker in the meantime - so I can continue working on the feature of my application - would be very appreciated 😄 )

However, I thought that a request to improve the documentation is worth its own issue.

Thanks, Kurt

@sippsolutions

This comment has been minimized.

Copy link

sippsolutions commented Oct 13, 2018

Any news on this - as this would be only a few lines of an explanation on how to build the request body to remove local tracks from a playlist? I have to do it manually now, which is a huge amount of work with 100+ playlists.

@nitricware

This comment has been minimized.

Copy link

nitricware commented Oct 14, 2018

Nothing yet unfortunately... I'm still waiting too...

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