Skip to content
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

fix: allow negative at start of entry #99

Merged
merged 2 commits into from
Nov 30, 2022
Merged

Conversation

iamkevla
Copy link
Contributor

allow the entry of negative at start instead of as is currently after first entering numbers

@apansky
Copy link

apansky commented Nov 10, 2020

Any chance of this being merged? Would solve my problem too..

@arg23
Copy link

arg23 commented Jan 28, 2021

Any chance of this being merged?

@JuanmaOrtizSisamon
Copy link

This is a good solution for me too :)

@leonandroid
Copy link

Hi guys, any chance this can be approved? It will solve a problem we are facing as well.

Copy link

@leonandroid leonandroid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, and looking forward for this to be released.

@antonioclaudioneiva
Copy link

This is a good solution for me too!

@KatyaBaranovskaya
Copy link

@nbfontana Could you answer if you plan to merge?

@ElChouaib
Copy link

SOS !! Please merge this pull request

@ElChouaib
Copy link

any intermediary solutions ??

@DywiTom
Copy link

DywiTom commented Nov 17, 2022

please merge!

@ArturQuirino
Copy link

Please someone merge this PR. It will solve a problem we are facing.

@nbfontana nbfontana merged commit d095e89 into nbfontana:master Nov 30, 2022
@nbfontana
Copy link
Owner

This is merged and I'm running some tests (it seems that this won't work with the natural type, only with the financial) I'm updating the natural type so that when we use the negative value as the first keystroke, we select all the remaining numbers and allow directly typing and changing the values...

Will release a 3.0 later today (cause I don't have too much time to test other edge cases and don't want to break current users of 2.*)

Sorry about the delay on this project (new jobs, new stuff on life, you get your mind on other priorities)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet