upvote

points

by sheept9 hours ago |
comments
upvoteby mort968 hours ago|
[-]
And then you end up with strings on the other side, not numbers.
reply
upvoteby sheept8 hours ago|
parent|
[-]
No you don't? The example I gave produces

    {"a":9007199254740993}
not

    {"a":"9007199254740993"}
reply
upvoteby mort965 hours ago|
parent|
[-]
Oh, that's much worse! The JSON string `{"a":9007199254740993}` decodes to the object `{"a":9007199254740992}` with typical JSON parsers like JavaScript's `JSON.parse`.
reply
upvoteby sheept1 hours ago|
parent|
[-]
If you're applying a replacer, then you'd supply a reviver when parsing:

    const json = '{ "a": 9007199254740993 }'
    JSON.parse(json, (_key, value, context) => /^\d+$/.test(context.source) ? BigInt(context.source) : value)
reply
upvoteby mort9655 minutes ago|
parent|
[-]
Yeah but now you have the world's biggest foot gun in your API.
reply