reformatting long integer issue

[kumarkiranm]

When I place a request of reformat and validate my json which contains a long integer, jsonlint is displaying the wrong output in reformatted json.

ex:
original: {"response":{"timestamp":1310033637419,"body":{"session":4261667034108713961},"type":"xxxxxxxx","version":"0.1.0.0"}}

reformatted:
CONVERTED:
{
"response": {
"timestamp": 1310033637419,
"body": {
"session": 4261667034108714000
},
"type": "xxxxxxxx",
"version": "0.1.0.0"
}
}

In the above example, "session" value is being modified by jsonlint while reformatting. not returning the original value.

Cheers,
KK

[umbrae]

To clarify, this has to do with maximum integer size in javascript. If you enter into the console: console.log(4261667034108713961), 4261667034108714000 is returned.

Ideally, we'd detect if a number passed is greater than the maximum integer size and issue a warning. As a simpler workaround, we could just use the string-based reformatter so that javascript number parsing doesn't get involved.

[kumarkiranm]

Either issuing a warning or parsing as a string if its greater than the max integer size will do. thanks.