[Fix] weight unit handling and UI updates #257
Draft
Conversation
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
…g in imperial units
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes Issue #256 in OpenNutriTracker, where weight inputs in pounds were rounded incorrectly, affecting precision.
What was done:
Implemented and tested precise unit conversion functions (kg ↔ lbs, g ↔ oz, ml ↔ fl oz).
Ensured user profile displays weight correctly based on chosen units.
Updated onboarding UI to dynamically change the weight label according to the selected unit.
Added automated tests covering conversions, profile display, and onboarding behavior.
All tests now pass successfully, confirming accurate conversions, correct weight display, and responsive UI updates during onboarding.
Commit
Commit