-
-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent rounding on some units #7504
Labels
bug-s3
The bug is stopping a critical or non-critical feature but there is a usable workaround.
Comments
filipefurtad0
added
the
bug-s3
The bug is stopping a critical or non-critical feature but there is a usable workaround.
label
Apr 28, 2021
Looks like an imperial measures only issue. Moving this comment to openfoodfoundation/wishlist#219. |
4 tasks
4 tasks
Closing from merging PR #12950. |
github-project-automation
bot
moved this from All the things 💤
to Done
in OFN Delivery board
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug-s3
The bug is stopping a critical or non-critical feature but there is a usable workaround.
Description
Closely related to https://github.com/openfoodfoundation/wishlist/issues/6
There's some issues with rounding issues with units like L, inserting a value respective to a given unit appears in the "Display as" field as a decimal, with plenty of significant digits. (see pic/video below). This can easily appear in the shopfront.
A known combination is
Volume (L)
, with value0.7
; others have been observed.Expected Behavior
Inserting 0.7 should appear as 700 mL.
Actual Behaviour
Inserting 0.7 L appears as 699.99999999.... mL
Steps to Reproduce
Animated Gif/Screenshot
This value gets actually gets stored and is even displayed in the shopfront:
Update
This issue also appears on the inventory (https://github.com/openfoodfoundation/wishlist/issues/6) and Order Cycles page:
Workaround
You can edit the display as field and type any value, overriding the placeholder value.
Severity
bug-s3: a feature is broken but there is a workaround
Your Environment
Possible Fix
The text was updated successfully, but these errors were encountered: