Tech
We Built Guardrails Against JSON Precision Loss. Then We Found Out Half of Them Weren't Actually Guarding Anything.
A few weeks ago I ran this through our own JSON repair tool, in the browser, on our own website:
json
{ "id" : 22233344455566677788 }
It came back as:
json
{ "id" : 22233344455566676000 }
No error. No warning. Just a quietly wrong number, presented as a successful repair.
That number is a made-up snowflake ID, the kind of thing you'd see as a primary key in a distributed system. And our own tool — the one whose entire pitch is ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to