mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 15:35:56 +03:00
[GH-ISSUE #85] Implement playlist folders #64
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @binyamin on GitHub (Aug 8, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/85
On the official Spotify clients, you can nest playlists under a given title. In other words, you can create folders filled with playlists.
I have a lot of playlists, and folders ensure my music is organized, and keep my sanity intact. Spotify's default styling should work fine with this interface.
👇 example 👇
[Folder title]
Playlist 1
Playlist 2
Playlist 3
@ShawkMusic commented on GitHub (Oct 26, 2021):
Yeah I would like to have this too
Makes organizing much easier
@jacksongoode commented on GitHub (Nov 22, 2021):
It looks like folders are unsupported by the API. I imagine it might be possible to create folders local to Psst?
Edit: There is a 3rd party solution if one has a Spotify cache present - might be a nice alternative. What do you think @jpochyla?
@jacksongoode commented on GitHub (Dec 2, 2021):
Just thinking that this could be feasibly rewritten in Rust and then add an optional import option in the account/preferences modal that would check the user's playlists against the cached folder structure on load and fill them in accordingly. Those playlists that don't exist in folders would appear outside.
It might also be helpful to have a remove button as well to drop the structure if desired. The parsed json could either be regenerated on load to look for changes or remain static until the user click's import again to update a changed folder structure.
new_with_namewithnew#420