Break endpoints up into different files so your design is modular. Create files for user, goals, workout, etc.
In main.py in /workout/{customer_id}, on line 62, use .scalar_one() rather than .first(). As Professor Pierce explained in lecture, this will result in safer code since we can only grab a single value from the query. Then, rather than using res.id, simply use res.
It is unclear what units you are using for height and weight. That should be clear in your documentation and your code.
Meal is very bare bones. I would suggest allowing users to add more information about meals they are consuming, such as food group, etc.
It appears that the /daily_calories/{customer_id} endpoint simply uses the first goal that was created by the user. For example, I ran Flow #1: Tracking daily calories and inputting workouts. I created a goal with a daily calorie intake of 2000, then had two meals totaling 2000 calories. I then created a new goal with a daily calorie intake of 5000. The /daily_calories/{customer_id} endpoint still returned that calories_left was 0, despite my updated goal. One solution to this would be to order the SQL query by date created (descending) and select the first goal.
In main.py, endpoints /workouts/{customer_id}/day on line 73 and /workouts/muscle_groups/{type} on line 95 both point to a function named "getWorkoutsByDay". Rename the getWorkoutsByDay function on line 96.
Endpoint /workout/{customer_id} causes an internal server error.
Suggestions for improvements:
Break endpoints up into different files so your design is modular. Create files for user, goals, workout, etc.
In main.py in /workout/{customer_id}, on line 62, use .scalar_one() rather than .first(). As Professor Pierce explained in lecture, this will result in safer code since we can only grab a single value from the query. Then, rather than using res.id, simply use res.
It is unclear what units you are using for height and weight. That should be clear in your documentation and your code.
Meal is very bare bones. I would suggest allowing users to add more information about meals they are consuming, such as food group, etc.
It appears that the /daily_calories/{customer_id} endpoint simply uses the first goal that was created by the user. For example, I ran Flow #1: Tracking daily calories and inputting workouts. I created a goal with a daily calorie intake of 2000, then had two meals totaling 2000 calories. I then created a new goal with a daily calorie intake of 5000. The /daily_calories/{customer_id} endpoint still returned that calories_left was 0, despite my updated goal. One solution to this would be to order the SQL query by date created (descending) and select the first goal.
In main.py, endpoints /workouts/{customer_id}/day on line 73 and /workouts/muscle_groups/{type} on line 95 both point to a function named "getWorkoutsByDay". Rename the getWorkoutsByDay function on line 96.
Endpoint /workout/{customer_id} causes an internal server error.