Repository navigation
fix(import): read Strong's measurements export as body weight - #591
Open
ConalMullan wants to merge 1 commit into
Open
ConalMullan wants to merge 1 commit into
ConalMullan wants to merge 1 commit into
Conversation
|
All contributors have signed the CLA. Thank you! |
Author
|
I have read the CLA Document and I hereby sign the CLA |
Strong exports body weight in a separate file (Date, Measurement Type, Value, Unit, Source) that the importer rejected as unrecognised. Read its Weight rows, each in its own unit, and skip the other measurement types. The import sheet now says "Import from Strong" for it instead of Apple Health. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ConalMullan
force-pushed
the
fix/strong-import
branch
from
October 13, 2026 21:54
fb9c6ef to
77ceb4b
Compare
ConalMullan
added a commit
to ConalMullan/openGym
that referenced
this pull request
Oct 13, 2026
|
Another shape of Strong's measurements export, in case it's worth covering here: mine came as |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Strong exports body weight as its own CSV, separate from the workouts file:
Settings → Data & backup → Import from another app rejected it as unrecognised, because the weight is in a
Valuecolumn and the row's kind is inMeasurement Type.What changed
parseBodyweightrecognises the file by itsMeasurement Type+Value+Datecolumns and reads theWeightrows only. Other measurement types (body fat, waist…) are skipped.Unit(kg / lbs), the way the Apple Health branch already handles mixed units (fix(import): convert Apple Health weights per record #432).docs/DATA_IMPORTS.mdmentions the file.Tests: three cases in
import-bodyweight.test.js: weight rows only, a per-row unit, and a file with no weight rows. Full frontend suite passes locally (5063). I also checked it against a real Strong 6 export with 48 weigh-ins.Related: #504 handles the rest-timer rows in the workouts export. This PR doesn't touch that file's parsing, so the two don't overlap.
🤖 Generated with Claude Code