fix, feat: multiple issue to-do list

[bfahrenfort]

Hi, I love the project!

Just wanted to document what I'd like to contribute soon. Each will be a separate PR. Please let me know if any of these are being worked on already or if you have implementation tips/design requirements!

• Import/export
  • feat: Save volume level as part of the state
  • feat: Sync settings via JSON export
• UX
  • feat: refactor "Next song" as "Queue" and add "Add to Queue", allow removal from queue as well
  • This one's a lot larger
  • feat: settings: text-match filter out of automatic Queue
  • ex. filter out "1 hour"
  • feat: collapsible callouts with tips on first load
• CSS
  • style: modify color variables for readability
  • Also a large project
  • fix: text visibility on Player background for some extracted colors
  • If the primary color is close to white, text is unreadable on light mode since it blurs through to the white app background

[stephane-r]

Hey @bfahrenfort

Thank you for your todo-list, several points are interesting :)

I can create an issue with a technical part if you wish, for each of the points raised. I have a question regarding import/export, point 1: I'm not sure I completely understood it 😄

Thank you again 👍

[bfahrenfort]

I'll create PRs as I implement them, no need to clutter the repo right now.

As for point 1 of import/export, if you refresh the page after having changed the volume, the volume will go back to 100%. I have very loud headphones so this is uncomfortable every time I open a new session. I want to save it in the same way settings are to persist across refreshes (cookies? Haven't looked at the codebase too deeply yet).

[stephane-r]

Aaaah yes for volume, good idea. We can add other switch in Settings/Player section.

All settings are save in localStorage by using local "database" with localstoragedb package. You can see this part in src/database folder. You'll need to create new migration for add volume.

Thank you !