Releases: s-yadav/react-number-format
Releases · s-yadav/react-number-format
v3.2.0: - Added event object as second param in onValueChange callback.
- Added event object as second param in onValueChange callback.
- Fixed #154
v3.1.0
V3 Release
- Refactor code for better stability
- Fixed issues with formatting and caret position in android chrome browser. #88
- Added support for numbers in prefix /suffix . Fix for #73
- Added support for phone number formatting and numbers in format. Fix for #81
- Added flowtype check
- Upgraded to react 16 and enzyme 3.0
- Fixed caret position when custom formatting is applied #97
- More accurate unit testing by simulating key inputs / focus and mouse events.
- Added a custom render method as props for displaying formatted value as text #86
- Added dynamic masking #83
- Standardize what can come as value props so plugin can make better assumption about formatting. #82
- Keep caret position withing typable area. #82 , #85
- Fixed preceding zero removal bug. #96
- Fixed incorrect behaviour when precision enabled and 0 with precision #70
- Make decimal scale fixed 0s optional #48
- Correct caret position on focus. Fixed #112, #85 (PR from @pandaiolo)
- Correct intermediate input on blur event. Fixed #96
- Fixed #77, #75 (PR By @isnifer, @adamshone)
Version 2
- Added isAllowed prop to validate custom input and reject input based on it. Fixes #23, #60
- onChange api been changed. Now it receives values object as second parameter. Fixes #71, #45
- decimalSeparator no longer support boolean values. Fixes #39
- thousandSeparator accepts only true as boolean (which defaults to ,) or thousandSeparator string
- Validate thousandSeparator and decimalSeparator a and throw error if incorrect props provided.
- decimalPrecision only accepts number . Fixes #66,
- Value prop is rounded off to provided decimal precision. decimalPrecision can be 0 if only integer value is allowed . Fixes #61, #44, #33
- Value can be passed as string or number but if it is passed as string you should maintain the same decimal separator on the string what you provided as decimalSeparator prop. Fixes #43
- Added back the type prop for the input type attribute (Only text or tel is supported). #35, #13 (PRs from: @kentandersen, @lgraubner)
- Fixed mobile issues #64, #52, #27 (PRs from: @stutrek)
- Fixed IE Issues #49, #8
- Fixed prop change effects after the component been initialized. Fixes #62, #28
- Enforce cursor to be between prefix and suffix in focus, click or arrow navigation. Fixes #29
- Stopped using parseFloat and toFixed method and created custom methods for those as they were resulting in the exponential format for number greater than 2^23.
- Migrate deprecated PropTypes (PR from #51)
- Fixed #69, #65, #58, #40, #14, #55, #68
Support negative numbers
- Support negative numbers by @jagkum
Feature and bug fix release
- Support custom input (#24)
- Support custom decimal / thousandSeparator (#18)
- Support providing decimal precision (#15 PR By @styks1987)
- Fixed mobile cursor issue (#27)
- Fix delete key issue (#21)
- Fixed delete key getting invoked twice (#30)
- Updated to enzymes for writing test case (#32)
- Updated from input type tel to text. Otherwise, user will not be able to type custom decimals.