[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
Your first Users route GET /api/users is a collection route pertaining to a singular user's profile. Again, the profile page should not be one of your main features at this point, but that being said, you might want to change this to a member route instead.
For your Business routes, the descriptions pertain to Session routes.
For your Review routes, the API resource is biz instead of reviews.
Backend Routes
snake_caseGET likesapi endpoint because that info comes through the post showComments
GET /api/usersis a collection route pertaining to a singular user's profile. Again, the profile page should not be one of your main features at this point, but that being said, you might want to change this to a member route instead.bizinstead ofreviews.