Feature
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start by reading the Flutter app’s workout logging and history screens, then trace how it calculates weekly muscle group sets and applies the activity map color theme. The issue combines several separate requests, including per-set notes, cardio logging fields, and secondary muscle group calculations; clarify the intended scope with maintainers before choosing an entry point. Done means implementing and documenting one agreed feature with its behavior verified in the app.
Written by the indexing model from the issue text.
Description
If you set your week to start on Monday, and end on Sunday the app should reflect "sets done per muscle group for that week" or at least have a setting for it . Not just a rolling 7 day period. It is way easier to track that way. Just a complete easy to read "font size " complete muscle group list with the amount sets done for that muscle group for the week.
Color theme change for activity map / heat map should change the colors of the whole app. Start button line graphs ect all of it.
Again notes per set that" stay in your history" not "just the exercise" but the history as well .. per set. When I look up past sets for example or the past times I have performed that movement it should allow me to see an note for every individual "set performed on that exercise on that day"
Logging, weight and distance, weight and time reps and distance , reps and time
Also please reconsider. Adding for cardio the following. Treadmill incline and steps or fights stair master.
Please add an explanation of how your calculating secondary muscle groups or add the options to set the number yourself as far as how many sets of the primary make a set for the secondary
- 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
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 5 days
Similar issues
-
priority: high scope: frontend type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GonsiorHack/czyPrzejade#15 ·
-
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
-
ORMOpenBackend SW VTA
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
aau-giraf/visual-tangible-artefacts#376 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day