Skip to content

Releases: s-yadav/react-number-format

Bug fixes and Test + Build upgrade

01 Jun 13:33
Compare
Choose a tag to compare

Test and Build improvements

  • Migrated test suite to vite, JSdom and react testing library, from Jasmine and Karma. Plus, a lot of fixes around the false negative test. Shout out to @aashu16
  • A couple of build improvements @aashu16
  • Unnecessary files are no longer included on npm package. Fixes #840
  • Added a better way to find change range which fixes issues around duplicate subsequent characters giving incorrect change range causing inconsistent caret positioning.

API Improvements
onValueChange now fires always if there is any change on the input, weather update comes from props or user events. This makes the callback more predictable. Fixed #812, Thanks to @rfviolato

Other Bug Fixes

  • Fix issue when complete text is selected and replaced with new value in pattern format. It was it was incorrectly pasting value.
  • Fix key press after selection over masked area. #839

Bug fix

17 Mar 17:56
Compare
Choose a tag to compare
  • Fix caret position not getting corrected when there is selection in the input. #780

Bug fixes

25 Feb 19:48
Compare
Choose a tag to compare
  • Fix caret position getting reset on jest + testing library. #814 by @csantos1113
  • Fix: pass currentTarget to onFocus. #815 by @csantos1113
  • Fix #817, wrong caret position getting set when . is pressed on empty value and fixedDecimalScale is set.

Bug fixes

03 Sep 16:11
Compare
Choose a tag to compare
  • Fix infinite rerender when values.value is used valueIsNumericString not provided. #786
  • Fix for delete of decimalSeparator happening when fixeDecimalScale is set. #789

Bug fixes with NumberFormatBase API improvement.

13 Aug 18:13
Compare
Choose a tag to compare
  • Fix #774
  • Added support to inform rnf to treat two character as same.
  • Fix custom numeral example
  • Documentation improvement, @gregfenton, @minervabot

Bug fixes

20 May 04:33
Compare
Choose a tag to compare
  • Fix for prop values on not updating (not reflecting on input) on StrictMode. Regression of v5.2.0
  • fix(number_format_base): prevent warnings in SRR when using useLayoutEffect. by @NicolasMontone

Regression fix from 5.2.0

15 May 02:52
Compare
Choose a tag to compare

Regression fix: try to correct the value if the old formatted value is provided but the format prop changes

Bug fixes and valueIsNumericString prop improvement.

14 May 17:05
Compare
Choose a tag to compare

Improvements

  • Optimize rendering, and avoid multiple rerender when number format is mounted.
  • Try to guess valueIsNumericString based on props and value, so the user no longer has to define this prop, if the format prop (prefix/ suffix for numeric format, format prop for pattern format) doesn't have the number in it.

Fixes

  • Fixes #736 - Fix for focus on mount getting reset.
  • Fixed #740 - fixed type for the format, removeFormat, getCaretBoundary.
  • Fixed #741 - Thousand and decimal formatting broken while typing when value isNumericString is set to false
  • Fixed #742 - cursor position getting changed when format props are updated during typing.
  • Fixed #725 - The cursor position not being correct when allowed decimal separator is typed
  • Fixed a couple of false positive tests and some regressions around those.

Bug fixes

05 Mar 15:49
Compare
Choose a tag to compare
  • Fixed #694 Prefix/Suffix containing numbers gets appended to value.
  • Fixed #691 Prefix/Suffix blocking input when set to a number
  • Fixed #729 Prefix '-' does not allow to remove first number
  • Added fixedDecimalScale prop to doc #735 by @arminbashizade

Bug fixes

10 Jan 18:31
Compare
Choose a tag to compare
  • Fixed #712 (Extra character added if you start typing from start of the input while input is fully filled)
  • Fixed #711 (The caret is not moved when typing a decimal separator at an existing decimal separator)
  • Mark module as side effect free (#713 by @topaxi )
  • pass type parameter to SyntheticEvent in event source object. (#703 by @yukiyokotani )