Open gyanendrasinghpanwar opened 8 months ago
I believe this has more to do with JavaScript limitations rather than this library limitations. Do you have an example number that causes failures?
I believe this has more to do with JavaScript limitations rather than this library limitations. Do you have an example number that causes failures?
"Indeed, this is more with JavaScript limitation. Currently, the number component is working accurately with up to 15 digits; after that, there is data loss due to parseFloat."
Do we have any plans to provide BigInt support in the number component or to offer number validation in the textfield component so that it can be used from there?
Let me know if need any Pull request.
hello i used this work around on the calculated Value logic const inputValue=data['test']; if ((inputValue.length>15)) { value=parseFloat(inputValue.replace(".","").substring(0,15)); }
I presume this due to below function in Number.js where we have used parseInt.
parseNumber(value) { // Remove delimiters and convert decimal separator to dot. value = value.split(this.delimiter).join('').replace(this.decimalSeparator, '.');
}