Technical Debt

[jordonet]

Description

Address technical debt and improve code quality.

Notes

Some thoughts I've had surrounding the config:

Store the runtime settings in the database, treat config.yaml as the initial defaults/bootstrap. On startup, merge config.yaml into the database if values don't exist yet, but UI changes write to the database only. That way:

• Fresh install: config.yaml seeds everything
• UI changes: persist to database, survive container restarts
• User wants to reset: delete the database row, next restart pulls from config.yaml again

Tasks

• SlskdClient typed error hierarchy
• Client-side runtime validation (Zod)
• DownloadTask state machine

[morgenman]

Heyo I have this up and running on my server. One issue I have is whenever the database is doing something I get a SQL lockout which silently fails in the frontend.
I figured this would be a good place to mention it. Thanks for the cool tool!

[jordojordo]

Hey, thanks for the feedback! I'll add that to the list of things to tackle