As I was trying to debug https://github.com/spotDL/spotify-downloader/issues/2067, I of course tried to fix my own web-ui at least temporarily by editing the web-ui files. That's when I realized the web-ui is downloaded every time spotdl web is invoked. This means the web-ui can't really be modified as it will just be overwritten again. It's also probably not very fast.
Possible implementation
It might be useful to check for the presence of the web-ui files before attempting to download them from the github repo. This would allow users to make lasting changes to their own web-ui. Something like --force-update-gui could be used to ignore the presence of web-ui files.
There could be an option to specify a path to web-ui files (--gui-source) so an advanced user could easily have it point to an alternative ui.
Requested Feature
As I was trying to debug https://github.com/spotDL/spotify-downloader/issues/2067, I of course tried to fix my own web-ui at least temporarily by editing the web-ui files. That's when I realized the web-ui is downloaded every time
spotdl web
is invoked. This means the web-ui can't really be modified as it will just be overwritten again. It's also probably not very fast.Possible implementation
It might be useful to check for the presence of the web-ui files before attempting to download them from the github repo. This would allow users to make lasting changes to their own web-ui. Something like
--force-update-gui
could be used to ignore the presence of web-ui files.There could be an option to specify a path to web-ui files (
--gui-source
) so an advanced user could easily have it point to an alternative ui.