* A few days ago, you reviewed the #BB-806 issue, I understand your concern regarding the backend submission failure, but after testing the changes locally, I found that when using parseFloat, the value remains as a float (e.g., 5.5), which provides proper visual feedback to the user if they enter a float.

However, when using parseInt, a value like 5.5 gets converted to 5, which leads to an error on submission because the input is no longer a valid float.

To address this, I switched to using parseFloat to preserve the float value and ensure that the validation is both correct visually (i.e., informing the user about incorrect input) and on submission.

I'll share a screenshot to show the result. Also, just to clarify—before moving forward with this solution, I asked whether the database schema should be modified to accept float values or if we should focus on frontend validation. Given your response about backend concerns, I’m still unsure what the final direction should be. Should we keep focusing on the frontend validation, or is there a longer-term plan to update the database to handle float values?

Thanks for your input!