Mara/progress

[mfunkel]

What has been done?

This PR adds "progress" functionality and includes frontend updates to the Profile Page, as well as backend updates to the History services and routes, and Profile service to enable progress tracking.

Summary Backend

• src/services/history-service.js - add function to gather data in correct format for progress tracking
• src/routes/historyRoutes.js - add route for getting progress data (top 3 most common exercises with correct data format)
• src/routes/workoutRoutes.js - updated to store history data for weight and reps as numbers instead of strings
• src/schemas/Profile.js - updated to store weight as array of objects (objects have unix timestamp and weight value)
• tests/unit/history-service.test.js - add test for progress tracking data fetching
• tests/unit/profile-service.test.js and profileRoutes.test.js - adjust profile tests to account for new storing of weight entries

Summary Frontend

• added recharts module to handle graph generation for progress tracking
• adjusted all profile fetching functions throughout all pages to sort weight array based on timeStamp field
• updated AddEdit.jsx and ProfileDetails profile components to enable storing user's weight changes with timestamps as opposed to simply the current weight
• created Progress Page to show user's top 3 most commonly completed exercises' weight progress, and the user's body weight logging entries
  • includes src/app/progress/page.jsx page to fetch the required data and house the graph components
  • includes src/components/progress/ProgressGraph.jsx component to display top 3 exercise progress graph
  • includes src/components/progress/WeightGraph.jsx component to display weight logging graph

Usage

• ensure a profile includes some history entries, ideally with a range of exercises, dates, and weights
• navigate to progress page
  • notice the top 3 exercises are graphed for average weight completed during each history entry
  • notice the weight logging graph to show all changes logged through updating user's profile

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fit-future	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 7, 2024 6:55pm
fit-future-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 7, 2024 6:55pm

[mfunkel]

don't think there would be any issues with the changes you made to the workout routes file as you are just modifying the data type before the history object is being created. shouldn't result in any issues, but may just have to verify that things that require access to the history object still work as expected, for example in starting a workout and viewing the recent history. github may complain about a branch conflict, but from looking at your changes i think it should be okay to just use your version as the only change you made is that for loop within the for loop to modify data types

Yeah, while I was implementing the change of data type stored in db, I checked that the start workout's recent history still shows the correct info, so it should be good to go. I resolved the conflicts that github was complaining about, so it should be fine to merge in that regard.