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
I think it might be better to do things like turning ArtistObjectSimplified[] into a string of comma-separated artists, or getting the name and image url out of AlbumObjectSimplified in the backend instead of multiple places in the frontend. This will also help with mocking track data for the add state, like #70.
Things to possibly change:
/api/playlists/:id/:
turning ArtistObjectSimplified[] into a string of comma-separated artists
getting the name and image url out of AlbumObjectSimplified
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.
I think it might be better to do things like turning
ArtistObjectSimplified[]
into a string of comma-separated artists, or getting the name and image url out ofAlbumObjectSimplified
in the backend instead of multiple places in the frontend. This will also help with mocking track data for theadd
state, like #70.Things to possibly change:
/api/playlists/:id/
:ArtistObjectSimplified[]
into a string of comma-separated artistsAlbumObjectSimplified
/api/playlists
response as described in Refactor/api/playlists
endpoint #74 (done)All of these should be done for all applicable endpoints, like
/api/playlists/:id
,/api/playlists
,/api/search
, and maybe more.The text was updated successfully, but these errors were encountered: