have a good think about my exercisesOrder thing, it is fragile, not enforced on backend. #108
Labels
No labels
bug
documentation
duplicate
enhancement
feature idea
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
davenh99/progressa#108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
easy, add hook to on routine/session record crud methods, check that all exerciseRows present in exercisesOrder, and no extra. if extra, delete. If missing, append at end.
then make sure the call to update the routine/session always happens after calls to routineExercise/sessionExercise... is this ideal?