[UI/UX] Refund float price #234
Merged
Conversation
This file contains 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
Jibbarth
approved these changes
Dec 9, 2020
|
It's possible to specify min/max over there as well. What do you think? Works alright on my project. |
oallain
approved these changes
Dec 10, 2020
GSadee
approved these changes
Dec 22, 2020
|
Thank you, Nicolas! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use number type field instead of the text type.
The web browser will send the value formatted correctly if we use 8.5 or 8,5.
Right now on master if we put 8,5, only 8.0 is refunded but with this fix, the decimals seperated by comma are taken into account.