fix session exercises dropsets and sorting order #177

Closed
opened 2026-07-29 18:49:06 +10:00 by davenh99 · 0 comments
Owner

dropsets are buggy, not clear how supersetParent works. sorting gets mixed up with this.

Proposal:

  • add 'sequence' field, to replace exercisesOrder. -> only set on rows without a 'supersetparent'
  • replace all backend duplicate row, import routine, code, to frontend (in preparation for offline first).
  • importRoutine into session or routine needs to allow copying also a session into a session
  • need to consider if data needs migrating after doing above, to suit new thingy. (it will need migrating, just how technical, do i need to fix some broken dropsets). -> looks like exercises all pointed to the singular supersetparent
  • for supersets, they are made up of a 'chain' of links. adding dropsets, and deleting, needs to consider this.
  • timeStart will be set on the first of the superset, and timeEnd on the last. it makes the highlighting tricky when recording but whatever. tick off each row of a superset individually, they all get timeStart and timeEnd
dropsets are buggy, not clear how supersetParent works. sorting gets mixed up with this. Proposal: - add 'sequence' field, to replace exercisesOrder. -> only set on rows without a 'supersetparent' - replace all backend duplicate row, import routine, code, to frontend (in preparation for offline first). - importRoutine into session or routine needs to allow copying also a session into a session - need to consider if data needs migrating after doing above, to suit new thingy. (it will need migrating, just how technical, do i need to fix some broken dropsets). -> looks like exercises all pointed to the singular supersetparent - for supersets, they are made up of a 'chain' of links. adding dropsets, and deleting, needs to consider this. - ~timeStart will be set on the first of the superset, and timeEnd on the last. it makes the highlighting tricky when recording but whatever.~ tick off each row of a superset individually, they all get timeStart and timeEnd
davenh99 added this to the v0.5.0 milestone 2026-07-29 18:49:06 +10:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
davenh99/progressa#177
No description provided.