[BUG] JEFIT import fails because # characters are not recognised
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
Research direction
The JEFIT detection and section extraction live in lib/services/workout_import.dart around lines 346-348; start by reading that file and locating where the ### EXERCISE LOGS ### heading is matched and where section bodies are extracted. Adjust both regexes to allow extra decorative # characters, then test with a JEFIT CSV whose headings look like ### EXERCISE LOGS ####. Done means the file is detected as a JEFIT export and the expected date, exercise, reps and weight columns are parsed.
Written by the indexing model from the issue text.
Description
What's wrong?
Importing a workout history CSV exported from JEFIT fails with the following error:
That file needs date, exercise, reps and weight columns
The exported file contains valid workout data, but GymMane does not recognise it as a JEFIT export.
I inspected the export and found that JEFIT uses section headings with decorative # characters.
### EXERCISE LOGS ####################################
JEFIT detection regex in workout_import.dart currently expects the heading to end immediately after three closing # characters CODE
RegExp(
r'^\s*###\s*EXERCISE LOGS\s*###\s*$',
multiLine: true,
caseSensitive: false,
)
Because the actual headings contain additional # characters, the file is not detected as a JEFIT export. It subsequently falls back to the generic CSV importer, which cannot find the expected columns.
Suggested fix:
Make both JEFIT detection and section extraction tolerate additional decorative # characters.
Where in the app:
Settings → Import from another app
- Dominant language
- Dart
- Stars
- 844
- Forks
- 98
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 11
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
-
KeyboardOpen
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
InlitX/GymMane#394 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
InlitX/GymMane#392 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
Similar issues
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day