You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #2760 some unwanted changes have been introduced together: HIX value is shown as 9 instead of 9.73 and mouseover does not show the detailed HIX value anymore
Steps to Reproduce
Activate HIX in Region Augsburg (in the local emvironment), set the user language to German
Populate pages with HIX value by ./tools/integreat-cms-cli hix_bulk augsburg
Go to the page "Gesundheitsamt" (for example), whose raw HIX score is 9,72960372960373.
See "9" in the HIX bar and mouseover doesn't show anything
Expected Behavior
It shows "9.73" and mourseover reveals the exact HIX score "9,72960372960373"
Actual Behavior
It shows 9 and mouseover doesn't do anything
Additional Information
The problem 9 vs 9.73 can only be observed if German is selected in the user setting. This is due to the different style between German (9,73, with comma) and English (9.73 with dot) and parseFloat().
you show HIX-value with 2 comma digits e.g. 9.73 and NOT as 9
The rounding up works well. So 9.735 is shown AND handled as 9.74. So if we would decrease the MT-threshold to 9.74, a value with 9.735 should work to translate
Describe the Bug
After #2760 some unwanted changes have been introduced together: HIX value is shown as 9 instead of 9.73 and mouseover does not show the detailed HIX value anymore
Steps to Reproduce
./tools/integreat-cms-cli hix_bulk augsburg
Expected Behavior
It shows "9.73" and mourseover reveals the exact HIX score "9,72960372960373"
Actual Behavior
It shows 9 and mouseover doesn't do anything
Additional Information
The problem 9 vs 9.73 can only be observed if German is selected in the user setting. This is due to the different style between German (9,73, with comma) and English (9.73 with dot) and
parseFloat()
.For more information and context, see #2756
Traceback
The text was updated successfully, but these errors were encountered: