Backend Routes

[KevinHJo]

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

    Comments

• Do you need a separate GET /api/profiles route, or can you use a backend association in the users controller to send profiles when you send a user?
• If you have access to all of a user's profiles upon login, will you ever need to send specific profiles one by one?
• When writing your routes, think about how you'll be using them. When will you need each piece of information, and can you get that information when you receive a related piece of info

[hwkcode]

• [DONE - Agreed. Deleted GET /api/profiles] Do you need a separate GET /api/profiles route, or can you use a backend association in the users controller to send profiles when you send a user?
• [ONGOING - Would like to discuss further] If you have access to all of a user's profiles upon login, will you ever need to send specific profiles one by one?
• When writing your routes, think about how you'll be using them. When will you need each piece of information, and can you get that information when you receive a related piece of info