Rotation: allow Rest steps anywhere in the cycle
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading how rotations advance after a workout is completed and how the home screen decides which workout and reminders to show; the issue does not name files or tests. Then trace how existing nutrition rest-day goals and calendar entries are represented. Done means rotations can include multiple Rest steps at any position, advance those steps appropriately, and preserve current behavior for rotations without Rest steps.
Written by the indexing model from the issue text.
Description
App version: 1.6.0
Problem
My plan is an 8-day cycle that ignores weekdays:
Push (strength) → Pull (strength) → Legs (strength) → Rest →
Push (hypertrophy) → Pull (hypertrophy) → Legs (hypertrophy) → Rest → repeat
The new Rotation (A/B/C) is almost perfect for this, but it has no rest step.
After Legs it suggests the next Push right away, even though my next day is Rest. On rest days I also get the "you haven't trained today" second reminder.
Proposal
Let users add Rest steps to a rotation, at any position and more than once (my cycle has two, in the middle and at the end).
Since a rest day has no workout to complete, it needs another way to advance. Two ideas, either would work for me:
- The Rest step advances on its own once its day has passed, or
- The home screen shows "Rest day" with a button to mark it done / skip it.
Nice to have
- No workout reminders on a rotation rest day.
- Show rest days in the calendar.
- Use the existing nutrition rest-day goals on those days.
Current rotation behaviour (advance when a workout is completed) would stay as it is for everyone who doesn't add a Rest step.
Thanks for the app, and for adding Rotation so quickly!
I'm happy to test a build if that helps.
- 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 67/100
Maintainers usually reply within 5 days
-
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
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 5 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Tencent/tdesign-flutter#1229 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
VeryGoodOpenSource/very_good_analysis#254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
berkmancenter/frankly#732 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rodydavis/signals.dart#510 ·