FSP Backend and Frontend Routes

[mwmadsen67]

Backend Routes

• [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
• [x] 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

---

Frontend Routes

• [x] Frontend routes contains wildcard variables written in camelCase
• [x] Correctly formatted
  • [x] Routes are displayed with inline coding text (backticks)

[mwmadsen67]

Hi Brendan, a couple notes:

Backend Routes:

• I noticed you have a route for GET /api/users to get account info for one user. This should be listed as GET /api/users/:id since it is only for one user. This also brings up a larger point that I may have glossed over in your feature list. Having a profile page where you can update your user's info is something that I would consider as a whole feature separate from user auth, so I would think about whether or not you want to implement that feature instead of another one or if you want to make it a bonus.
• cart items looks good. Keep in mind that only reason you don't need to nest the GET cart_items route under user_id is because you can just use the current_user.
• products and reviews looks great too.

With this I would say you're finished with your design docs! Nice job! Let me know if you have any additional questions getting started.

[mwmadsen67]

just kidding I forgot to look at your frontend routes

[mwmadsen67]

Frontend Routes:

• for all the product categories, I would not list these as separate frontend routes with different components. I would put this as /products/:category and put ProductIndex underneath. You could consider "all" to be a category as well. The reason for this is ultimately you would just be using the same component for each one and just listing different stuff.
• In order to avoid a route conflict with the ProductShow page, I would name it something else like /product/:productId or /product-item/:productId, something like that.

Otherwise yeah its all good