Design Docs Review #3

[rlim92]

Hey Olga! Routes are looking good. Suggestions below:

Frontend Routes

• [x] /workouts/workoutId/new no need for this route as the previous route will take care of the new workout form.

Backend Routes

• [x] will need a user show route to get to UserProfile.
• nested route showing a user's route is good.
• [x] should add a regular route index route as well. This can be bonus later for segments but it looks like we can search for routes near our location. This would be a cool use of google Maps API too.
• [x] GET /api/workouts should nest this route and and include a user_id because one can see another's workouts on their profile.

[pauchye]

Frontend Routes:

1. updated it to be an edit route Backend Routes:
2. i believe i have one GET /api/users/:id - user's show page (user's info and stats)
3. added but want to discuss. do we have 2 routes for routes index page?
4. updated it to be nested under user_id

[rlim92]

Hey Olga,

3. We should eventually have 2 routes because we should see our own routes we made and then we should see segments which look to be like public routes that one can take if they want. We can leave the second route for bonus.