You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, when a track is removed, the track and its chat will get fully deleted from the database (obviously they are deleted from Spotify too, that behavior won't change). This also means re-adding a removed track will be no different from adding an entirely new track.
Also a side note — I don't think I will implement user guards against adding a track that already exists for Milestone 1. Not sure what will happen in that situation: the DB insertion might fail while the Spotify insertion succeeds (Spotify allows the same track to be added multiple times), so the DB and Spotify would be out of sync but the client would just see the DB tracks.
The text was updated successfully, but these errors were encountered:
For now, when a track is removed, the track and its chat will get fully deleted from the database (obviously they are deleted from Spotify too, that behavior won't change). This also means re-adding a removed track will be no different from adding an entirely new track.
Also a side note — I don't think I will implement user guards against adding a track that already exists for Milestone 1. Not sure what will happen in that situation: the DB insertion might fail while the Spotify insertion succeeds (Spotify allows the same track to be added multiple times), so the DB and Spotify would be out of sync but the client would just see the DB tracks.
The text was updated successfully, but these errors were encountered: