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(input-amount): returns Unparseable as a modelValue if a wrong value has been entered #2242

Merged
merged 4 commits into from
Apr 10, 2024

Conversation

gerjanvangeest
Copy link
Member

@gerjanvangeest gerjanvangeest commented Apr 3, 2024

What I did

  1. fix: return Unparseable if characters other then a number are typed.
  2. fix: [LionInputAmount] uses NaN where Unparseable would be preferred #2233
  3. fix: [@lion/ui/localize.js] parseNumber('--42') is parsed as NaN #2227

Copy link

changeset-bot bot commented Apr 3, 2024

🦋 Changeset detected

Latest commit: 0f49477

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@lion/ui Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@gerjanvangeest gerjanvangeest force-pushed the fix/input-amount-unparseable branch from 0ad8933 to ca09446 Compare April 3, 2024 12:28
@gerjanvangeest gerjanvangeest force-pushed the fix/input-amount-unparseable branch from ca09446 to 87f864f Compare April 3, 2024 12:34
@gerjanvangeest gerjanvangeest force-pushed the fix/input-amount-unparseable branch from 6e47def to 190d8a9 Compare April 9, 2024 12:45
@tlouisse tlouisse self-requested a review April 10, 2024 09:11
@gerjanvangeest gerjanvangeest merged commit e8e9c07 into master Apr 10, 2024
5 checks passed
@gerjanvangeest gerjanvangeest deleted the fix/input-amount-unparseable branch April 10, 2024 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants