Parsing amount with JSON.parse

Question

Dos it exist a maximum float number with two digits after decimal point that can be parsed with JSON.parse without losing precision?

For example:

JSON.parse('{"amount": 9999999999999.99}')

{amount: 9999999999999.99} // not lose (probably)

JSON.parse('{"amount": 99999999999999.99}')

{amount: 99999999999999.98} // lose

Yes there is a limit. See [this answer](https://stackoverflow.com/a/9643650/535480) for more details. — James, Mar 02 '18 at 18:01
But this topic did not answer the question what exactly is the value. Number.MAX_SAFE_INTEGER is much bigger number. — ku8ar, Mar 02 '18 at 18:23
Right but you don't have an integer there. So the number of significant digits you can store accurately with all 9's (the highest possible decimal value of that precision) is fifteen. Your first number has fifteen significant digits, your second number has more and doesn't work as expected, because you've run out of precision. — James, Mar 02 '18 at 18:24

score 1 · Accepted Answer · answered Mar 02 '18 at 19:45

If x is a decimal floating-point number with 15 significant digits or fewer, then converting x to JavaScript’s Number type and then converting the result back to a decimal floating-point number with the same number of significant digits produces exactly x, provided the number is within normal bounds. Therefore, all decimal numerals with two digits after the decimal point from “.00” to “9999999999999.99” can be parsed, stored, and reformatted with two digits after the decimal point, and the result will be the original numeral.

The stored value will generally not equal the original value. For example, when “.99” is parsed, the result will be exactly 0.9899999999999999911182158029987476766109466552734375. However, the stored value will be sufficiently close to the original value that, when converted back to the original number of digits, the original value is recovered. Note that you must know the original number of digits; it is not inherently a part of the Number value.

15 is a lower bound for this property. There may be some exponent values for which all 16-digit decimal numerals survive a round trip. However, since 99999999999999.99 (16 digits) produces 99999999999999.98, we know this is not one of those intervals.

If you want to know the specific number between 9999999999999.99 and 99999999999999.99 where this round-trip property first fails, you may have to hunt for it computationally. It many not be a value that is easy to calculate directly by mathematical properties.

Parsing amount with JSON.parse

1 Answers1