staijn1 / spotifymanager Goto Github PK

Also allows for update for dependencies

e.g. available_markets can be filtered with expression fields=items(track(!available_markets,album(!available_markets)))

Multiple audio previews can be played at the same time making them mix together.

Turn all audio previews off when one is started.

Issue #2 calls for a simplification of the comparing process, which has now been implemented.

However, the more simple solution lacks some features that the old one had, but in a complicated way.

The current, simpler implementation does not let the user know that a song has been removed in the current original playlist vs the original playlist at the time of remixing.

How it will work:

• When remixing a playlist, store the current original playlist in a file / database, with a reference to the remixed playlist too.
• When syncing a remixed playlist, look up the state of the original playlist at the time of remixing, and compare it to the original playlist now.
• Then compare the original playlist now with the remixed playlist now.

Here are some example states

The comparison view to sync should display:

Currently, the song preview is stopped when you click one of the actions (add song back or keep removed).
When the preview is playing for song A, and an action is done for B, the preview is stopped, but that should not happen.

Only when the user performs an action for the song he is previewing, the preview should be stopped.

Document remixing process on the get-started page, by using this mermaid diagram:

edit

When the user is listening to the song preview, stop it when the user has clicked either the "move back to playlist" or "keep deleted" button

In the getAllTracksPlaylist method, each page of tracks in a playlist is requested one by one. We can optimize this method by using Promise.All() to fire all requests at the same time and awaiting all of them. This will be faster than requesting a page, awaiting the result, requesting the next and so on.

When you are about to remix a playlist, and you scroll down to automatically load the next page of songs, it will add playlists that are already on the list.

Add "padding" to the list of songs in the compare page, to make sure unchanged songs are at the same level.

As an example, let's take the following scenario:

The desired layout of the page in this scenario is:

Because track C and track F are changed (they are not in both playlists), the user can decide what will happen to these songs.
If the user decides to add track C back, the desired layout of the page in that scenario is:

The placeholder should be a component similar to the spotify-track component but with different styling to make it clear it's a placeholder (e.g. maybe make it greyed out, dotted borders or something else)

To sync a playlist, currently you need to compare the Current original playlist vs the Playlist at the time of Remixing.

This can be simplified since the current remixed playlists already has the songs from the playlist at the time of remixing (minus the ones the user did not like, and added with custom songs)

So only current original playlist needs to be compared with current remixed playlist

Depending on the email preference set for a user:

• Check if any of the original playlist has any changes. If so this playlist will be included in the email for that user

Show a spinning loading icon on initial page load when syncing playlist.
Also show a loading icon inside the Sync! button when clicked and the sync is running.