chunisama / dropify Goto Github PK

MVP List

• For Track / Playlist CRUD, I would hold off on implementing likes at this stage and focus on the CRUD for tracks and playlists.
• Search feature will rely on filtering by genre as well as by artist, album, etc.
• Timeline looks straightforward!

Schema

• As long as the only likeable entity is tracks, we can hold off on making likes a polymorphic association
• What does type refer to in the Albums table?
• The playlist_songs table looks great, we absolutely need a joins table and the added column of position will pose an interesting challenge. More on this in our meeting Tuesday.

Backend Routes

• GET /api/users should provide an :id specifying which user we're providing information on
• Songs should also have POST PATCH DELETE routes to create, update and delete songs
• Should we add POST for Artists? Eg. if I try to upload a song with a nonexistent Artist, we automatically create a DB record for that new artist? Let's talk about this as well
• Playlist_Songs should also support a PATCH request to update a song's position.

Frontend Routes

• I'll update this once these are added.

Sample State

• It makes more sense to me for each playlist in the playlist slice of state to have an array of song_ids instead of also including a playlist_songs slice of state

Keep up the great work! Looking forward to meeting this Tuesday.