Input not reformatting after value changes

[irt-msummers]

Description

If a value is changed programmatically the formattedValue doesn't refresh with fractionDigits. The $ is there but not the fractionDigits.

Version Used

0.11.3

Expected Behavior

It should show the fractionalDigits

Actual Behavior

It shows the fractional digits the first time and on a value that is a whole number but if you change to another whole number it doesn't show them. If you focus in and out of the inputbox it changes like it should.

Props Used

List down the props you used with the component, for example:

<CurrencyInput name="default" bind:value={formState.AskPrice} />

Reproduction Steps

I took your demo and just added a button click

https://svelte.dev/repl/20a823b0befe40ceb3fd3c4bd0b02bcb?version=4.2.10

1. Click change price in the example
2. If you leave the number the same it still shows it with the decimal places. As a test, I set askPrice to 22 and change it to 22 it still shows $22.00

Additional Info

• OS & Version:
• Browser & Version:
• Any other relevant details or potential solutions:

[irt-msummers]

IDK if this fixes it or what it might break

$:
value, setFormattedValue(true);

Which is used here:
formattedValue = isZero && !isZeroNullish ? "" : formatCurrency(value, fractionDigits, hasMinFractionDigits ? fractionDigits : 0);

Update:
NO -- it breaks it

[fmaclen]

Thanks for reporting this issue, I'll look into it.

[irt-msummers]

Thanks -- the only way I have been able to get around it is outside the component using #key

https://svelte.dev/repl/20a823b0befe40ceb3fd3c4bd0b02bcb?version=4.2.10

[fmaclen]

@irt-msummers I think I got it.

Here's the demo:
https://74-external-value-change.svelte-currency-input.pages.dev

And the code for the demo:
https://github.com/fmaclen/svelte-currency-input/pull/75/files#diff-1e1270da740e81dd13f8a65057582b0fce8a5fb3817ef913f3e90d7f82c4e9dfR116-R140

EDIT: it also works for your example:
https://ecbd9b1c.svelte-currency-input.pages.dev/test

Take a quick look at it and let me know if this does indeed fix the issue you described.
Also, would you be interested in reviewing the PR after I finish the test?

[irt-msummers]

Yes that seems to fix it on my application. Thank you so much!!!!

[github-actions]

🎉 This issue has been resolved in version 0.11.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[fmaclen]

@irt-msummers no problem, thank you!