Workouts Tab about fitnis HOT 4 OPEN

[](930c2c5)

from fitnis.

These arrows should only be rendered if there is something to expand

from fitnis.

Need to remodel how data is being set to backend

Front-End:

Collects and structures the data in an easily manageable format:

data: {
    programname: "...",
    exercises: [
    {
        exerciseid: "...",
        exercisename: "...",
        sets: [
            { set: 1, reps: 8, RPE: 7, Notes: "Felt good" },
            { set: 2, reps: 8, RPE: 8, Notes: "Tough but manageable" },
        ]
    },
   ]
}

Back-End:

Receives the data and processes it to fit the relational database schema:
Extracts the programname and creates a new workout program entry if needed.
Iterates through each exercise in the exercises array:
Checks if the exerciseid already exists or if a new record should be created.
For each set in the sets array, creates a new entry in the Sets Table with the corresponding exerciseid, reps, RPE, and Notes.

Database Operations:

The workout plan, exercises, and sets are all stored in their respective tables, with relationships defined by foreign keys.
This could involve multiple insert queries, potentially within a transaction to ensure data consistency.

from fitnis.

Front-end:

Step 1: Add exercises to workout cart
Step 2: Add desired amount of sets + info (reps, rpe, notes) to each exercise

• currently storing the number of sets per exercise like [3,3,3,4,5]
• Might be better to do like [[8,8,8],[8,8,8]] (2d array where each element in parent array is an array of reps)
• • if sets are needed can just find the length of the array
• • Could do a similar weight array type thing

Step 3: name workout

from fitnis.