Let a routine define its own progression (beyond the built-in 6 chains)
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
Research direction
Start at the routine edit screen, the existing superset toggle, and the custom routine import model named in the issue; then trace how level-up checks the built-in kProgressions table. Map how routine exercises are stored and how progression order could reach level-up prompts. Done means routines can define ordered exercise progressions and level-up considers them alongside built-in chains.
Written by the indexing model from the issue text.
Description
Right now level-up only checks the hardcoded kProgressions table — so any progression chain a routine needs beyond those 6, or any rung a built-in chain skips (the pull-up chain has no Arch Hang step between Scapular Pull-up and Pull-up Negative, the dip chain has no Support Hold step), never gets a level-up prompt.
I'd like routines to be able to mark a subset of their exercises as an ordered progression, the same way exercises can already be marked as a superset (chained). Level-up would then walk that routine's own progression too, not just the built-in table.
Where: Routine edit screen, next to the existing superset toggle, and the custom routine import model.
Use case: again the Reddit Recommended Routine, which has progression chains the app doesn't ship, and two of GymMane's own chains are missing a rung. ALso, generally speaking, hard-coding a chain cannot fit all the routines.
- Dominant language
- Dart
- Stars
- 844
- Forks
- 98
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InlitX/GymMane
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
InlitX/GymMane#276 · 1 comment ·
Maintainers usually reply within 5 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 5 days
-
Done enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
InlitX/GymMane#272 · 1 comment ·
Maintainers usually reply within 5 days
-
Health connectOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 5 days
-
FeatureOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 5 days
Similar issues
-
Push workflow fails: oversized artifacts cannot be pushed to `app` branchPossibly taken @marcnause claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fossasia/magic-epaper-app#724 ·
Maintainers usually reply within 1 day
-
priority: high scope: frontend type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GonsiorHack/czyPrzejade#15 ·
-
a: accessibility has reproducible steps p: cupertino_ui package team-design
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
fix: jaspr serve keyboard shortcuts (r/R/l/d/q) don't work on WindowsPossibly taken @lewinpauli claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
berkmancenter/frankly#729 ·
Maintainers usually reply within 1 day