5) Backend Routes

[cdellacqua123]

• [x] Contains the following sections: HTML, API Endpoints(Backend)
• [x] Each route has a description
• [x] API Endpoint routes contains wildcard variables written in snake_case
• [x] Routes does not contain superfluous routes
• [ ] Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

[cdellacqua123]

• Good work!
• Make sure HTML is all-caps
• Make sure that the carts represents what we discussed today in our 1:1. It looks like some routes with their description are still assuming one table/model for a user's entire cart (i.e. delete is deleting an entire cart) when it will be better if we have multiple orders that are updated/deleted/created/fetched at the user's request. You could have an Empty Cart button, but that would most likely be sending multiple requests to the backend from the front deleting multiple items. We can talk about this once you get the basics of the cart down!