Rework, refactor, revamp

[abcdefghijorngarbosaxyz]

Details

Rework the current web-ui using vue with typescript, vue-pinia for state management. Changes are based on spotdl CLI dev branch.

To-do

• Refactor to typescript
• Additional settings capabilities
  • Upload custom config file
    • Frontend
    • Backend
  • Bitrate
    • Frontend
    • Backend
  • Providers as list instead of single select
    • Frontend
    • Backend
  • Use YTM data
    • Frontend
    • Backend
  • Only verified results
    • Frontend
    • Backend
  • Generate lyrics
    • Frontend
    • Backend
  • Threads
    • Frontend
    • Backend
  • Force update metadata
    • Frontend
    • Backend
  • yt-dlp args
    • Frontend
    • Backend
  • ffmpeg args
    • Frontend
    • Backend
  • Output dir
    • Frontend
    • Backend
  • File format
    • Frontend
    • Backend
• Revamp UI
• Check for CLI, and web-ui updates Done on server side
• Download songs automatically instead of going to downloads and clicking download again #1864
• Display search, search results, queue in one page Canceled. Use vue-router instead
• Themes & theme changer (daisyui)
  • Forest
  • Light
  • Dark
  • Cyberpunk
  • Cupcake
• Miscs
  • Footer
    • New issue link
    • Docs link

Why and Motivation

My friends and I love to use spotDL. But using the web-ui feels like a bit "outdated", and we encountered some issues using it:

• When IDM is active, clicking download on downloads page passes the file to IDM, then the page reloads, shutting down the server. The same behavior with manually entering the http://.../download url in the browser is causing the server to shutdown as it returns { details: "not found" }. I guess it's normal on SPA apps as the server only has / route.

We noticed that web-ui repo is frequently inactive, so we've tried to work on our own version of it.

---

Please feel free to add some features you'd like to be implemented, on the todos list.

[xnetcat]

Additional settings capabilities

Settings should be generated automatically based on the settings model since they change quite often.

[abcdefghijorngarbosaxyz]

Additional settings capabilities

Settings should be generated automatically based on the settings model since they change quite often.

Im thinking of just getting the settings on the api/options_model so the web-ui stays updated with the CLI.

[abcdefghijorngarbosaxyz]

Will open a new PR from fresh fork.

Opened #11