Open yeoshuheng opened 2 months ago
It is unlikely that our target user (personal trainer) requires height to be recorded at such a high accuracy. Additionally, we think this qualifies as "extreme user input".
It is a valid issue, but fixing it is less important than the work done in the current version of the product.
Additionally, we did include the rounding behaviour it in the UG. (although it is incorrect, but that is not the bug being reported here)
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
edit 1 h/1.9222222222222222222222222222222222222222222222222
Causes the person in the first position to obtain a rounded height.
However, it is not known to the user how this rounding is being completed, are we rounding it down / up? To what decimal place is the rounding occurring, may be nice to have it in the UG too.