* Create a shared DragDrop Zone
- This zone allows the dropping of files
- The zone allows validation by parent
- The zone allows customisation like icon shown
* Import Settings
- Ability to import settings from a JSON file
- Validation to ensure file compatibility
- Visualiser for viewing string differences
* i18n
- Moved all hardcoded values to be en localised
* Zod / Validation
This commit contains the code to move settings to using ZOD, the reason for this is so that we can validate the settings schema that is being imported.
This commit also adds various validation and transforms to ensure the settings being reimported match values we expect.
I also removed the original crude validation and replaced it with the new ZOD parser that will handle this for us.
Finally the "styles-settings" component will listen to any external content updates and update its value, the reasoning is the external import wouldn't update the existing value.
- Split Settings schema into two parts, schema that is validated on import and schema that is not
- Schemas are merged to make the full SettingsStateSchema
* Migrate during validation
- Migration is done as part of validation
- Updated the store version to v10 as there has been changes to the settings
- Migrate will now add the fields from v9 to v10
- the build was failing due to ids not being mapped to their enum values
---------
Co-authored-by: Jeff <42182408+jeffvli@users.noreply.github.com>
* add web visualizer
* fallback to simple model
* less samples, hopefully more efficient
* Use audiomotion analyzer
- Note: fixed to 4.1.1 because 4.2.0 uses esm which breaks in the current workflow...
* revert publish changes
* r2
* don't massively change package.json
* lazy
* [scuffed bugfix]: Update table rating/favorite when updated anywhere else
Modify player store to have temporary state for favorite/rating update
Add effect handler for `virtual-table` to update rating/favorite for players
Note that this does not handle song grid view.
Using a similar handler for gird view did not work, as it appeared to result in inconsistent state.
Finally, this is probably not the optimal solution.
Performance appears fine for ~20k items, but no guarantees.
* restore should update song
* update song rating/favorite/played everywhere except playlist
* special rule for playlists
* use iterator instead