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

Removed tracks and re-adding tracks #89

Draft
wants to merge 8 commits into
base: develop
Choose a base branch
from
Draft

Conversation

Noam-Bendelac
Copy link
Collaborator

Draft pull request to resolve #87.

Close #88.

Add 're-add' action to situated and separate chat, add removedTracks
array to playlist document, and make PUT `.../:trackId/removed` support
re-adding removed tracks.
TODO add other checks for other endpoints like `.../:trackId/removed`?
@Noam-Bendelac Noam-Bendelac added this to the Milestone 2 milestone May 23, 2021
@Noam-Bendelac
Copy link
Collaborator Author

This will close #67 as milestone 1 removal behavior will not be necessary when this is implemented

Refactor api types for track search and tracks within
`.../playlists/:id` to have just the data needed by the frontend, and
move some of the processing from the frontend in several places to the
backend in one place.

These were done together so the draft addition track's data can be
mocked in `SearchResults.tsx` `addButtonOnClick` callback. This will now
allow spotify data on removed tracks to be saved when they are removed
for #87.
When there were multiple removed tracks and one of them was re-added,
the other removed tracks disappeared because I assumed that if I leave
off the second parameter to splice it would default to 1. (This behavior
likely varied depending on the position of the re-added track within the
removed tracks array, so maybe it didn't always happen).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant