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
Similar to what I did for the /api/playlists/:id endpoint and its response type in f5b375c and 044bd2e, I need to have better control over what data is forwarded from the Spotify API and decide exactly what parts are needed. This will help with state management in the frontend and mocking track data for the add state.
The text was updated successfully, but these errors were encountered:
This should include basing the GetTrackSearchResponse type on an array of TrackObjectFull (from TrackSearchResponse['tracks']['items']) instead of the broad SearchResponse type.
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.
Similar to what I did for the
/api/playlists/:id
endpoint and its response type in f5b375c and 044bd2e, I need to have better control over what data is forwarded from the Spotify API and decide exactly what parts are needed. This will help with state management in the frontend and mocking track data for theadd
state.The text was updated successfully, but these errors were encountered: