C19 Kunzite - Gabbby Y, Angelica Y, Areeg J, Amber S #41
Conversation
…res at each css changed the handling function over at cardlist
…pondingly receiving the function at Card to handle the button
…files so that a board has a bunch of cards inside
| return { | ||
| ...entry, | ||
| likes_count: entry.likes_count + 1, | ||
| }; |
There was a problem hiding this comment.
Rather than building a new card object directly here, make use of the card data returned from your PATCH call and insert that in place of the existing card. Currently, this duplictaes the increment logic which the backend is already performing (and which the backend should own).
| .post(kBaseURLCards, data) | ||
| .then((res) => { | ||
| console.log(res.data); | ||
| linkCardToBoard(res.data.id) |
There was a problem hiding this comment.
Rather than making a card that doesn't belong to a board, and then adding it to a board, consider using the nested POST route to directly create the card already belonging to the board. Task list did this as two separate operations since Tasks were allowed to not belong to a Goal. But here, all cards are expected to belong to a board. It shouldn't be possible to create a card that doesn't belong to a board.
| setBoardData((prevBoardData) => | ||
| [...prevBoardData, newBoard]) | ||
| console.log(response); | ||
| fetchBoards(); |
There was a problem hiding this comment.
👀 Since you're re-retrieving the board list here, there's no need to set the board data here as well. If you did want to just graft the new board data into the board list (without needing to re-fetch the whole list), be sure to use the result returned from the post call, as that board data would have the new board's id (which would not be present in newBoard, as that's only the data that came from the new board form).
No description provided.