Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temporary track removal behavior (Milestone 1) #67

Open
Noam-Bendelac opened this issue Dec 28, 2020 · 0 comments
Open

Temporary track removal behavior (Milestone 1) #67

Noam-Bendelac opened this issue Dec 28, 2020 · 0 comments
Labels
backend Backend functionality wontfix This will not be worked on
Milestone

Comments

@Noam-Bendelac
Copy link
Collaborator

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.

@Noam-Bendelac Noam-Bendelac added the backend Backend functionality label Dec 28, 2020
@Noam-Bendelac Noam-Bendelac added this to the Milestone 1 milestone Dec 28, 2020
@Noam-Bendelac Noam-Bendelac added the wontfix This will not be worked on label May 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend functionality wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant