-
Notifications
You must be signed in to change notification settings - Fork 121
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
Start input with a negative charachter #57
Comments
Hi @ulfojebo! There's this option: If you type 88 and then hit the minus button on the Keyboard the output becomes -88.00 (depending of your current config). The minus charachter also appears for the user in front of the current prefix. Is this a solution for your case? |
I know that it is possible to enter negative numbers that way but it seems unnatural. |
|
+1 to @ulfojebo request |
I have a same issue. |
Having the same issue. And of course -- it will be very helpful and made the lib more solid. Please merge it into main branch. |
@ulfojebo @betodasilva did you guys just clone the lib locally and made those changes in the changeToNegative? Or are there any other workarounds? |
+1 to @ulfojebo request. I also have clients who are used to entering the negative sign as the first value when entering a negative currency value. This feature would absolutely make the lib more solid. |
great, this is working once we edit the core files, @nbfontana could you please take a look at this , it becomes a very important feature now. |
This is a deal-breaker for us too. I used the above fix and it worked. but modifying the library is not a sustainable solution. |
Tried using this package and it works really well.
Would like to discuss the posibility to add a "minus" charachter as the first input in a field.
The users of the system my team is building are used to this workflow when entering numbers.
I made it work on my machine but the question is if you think it should be entered here or if I should fork this project and make my own version for my specific needs.
Thanks!
The text was updated successfully, but these errors were encountered: