-
Notifications
You must be signed in to change notification settings - Fork 106
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
Support Spotify playlist folder structure #61
Comments
If I remember correctly this is actually a bit tricky to do since we only get the flattened playlist names so any hierarchy has to be inferred. Unfortunately the path separator is a |
We've talked about exposing playlists in mopidy in a way that allows use to keep the structure. Essentially something similar to the browse interface, possibly even reusing the browse interface just using a playlists root URI. |
Is that in any of the roadmaps yet? |
Don't remember if this made it anywhere, it was originally something that I think came up as part of the "list" support. But the idea would be to have |
Although it's not a fundamental solution, maybe an additional setting that allows the user to set the depth of the folder structure? |
Moped extracts the folders using the / |
|
In fact I have added the code myself to do this (display folder structure). |
Thanks but I'm not sure. I believe it's on the Mopidy road map to address
|
First of all: thanks for all the good work, I use it a lot. I would like to propose the following enhancement as I structure my Spotify playlists using folders. Is it possible to support a foldable folder structure in the webclient? Personally I would like to have the folders unfold by default.
The text was updated successfully, but these errors were encountered: