You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @ujaehrig, yes this is due to the fact that Javascript only supports representing numbers up to 2^53-1 (usually encoded as a double but not necessarily). Not sure how to solve this tbh...
Yes, I checked the specs in the meantime and saw that JSON has only the double precision number type. My example had used Java-Jackson as JSON processor which can also handle long ints.
Nevertheless, it's unfortunate, that rq changes the value, even it's not touched directly. Maybe a warning (something like "int number too large" or "int number precision loss") could be the first solution?
When running an assign on a JSON with a large integer, the integer is changed. This might probably be caused by handling it as a double?
Example:
results in:
The text was updated successfully, but these errors were encountered: