[BUG]: int64 long type data is not supported. When the data exceeds int64, there will be a loss of accuracy

[aninstein]

Issue description

JS does not support long data type int64, but most server-side languages such as Java and Go support int64 data type, which can cause overflow in JS

Media & Screenshots

Operating system

• OS: [e.g. iOS]:
  macos
• Browser [e.g. chrome, safari]:
  edge
• Any other details...

Priority this issue should have

Low (slightly annoying)

[Prateek-Wayne]

I would like to pick this issue
Could you please assign this to me @AykutSarac .

[Prateek-Wayne]

We're encountering precision loss for large int64 values (e.g., 123456789012345343443) during CSV ,YAML and JSON serialization. This happens because our current parser setup does not preserve large integers accurately.

CSV output (via fast-xml-parser) truncates or rounds the number:❌

transaction_id
123456789012345343443

JSON output (via jsonc-parser) suffers from the same issue:❌

{
  "transaction_id": 123456789012345343443
}

YAML:❌

transaction_id: 123456789012345343443

XML:✅

<transaction>
  <transaction_id>123456789012345343443</transaction_id>
</transaction>

[Prateek-Wayne]

Possible solution that came to my mind is to preprocess the json string to wrap large numbers which are greate than >16 digits in quotes before parsing.

[Prateek-Wayne]

@AykutSarac Please let me know if you're okay with this direction. If it looks good, I’ll go ahead and raise a PR with this solution.

[AykutSarac]

We should show it as a number on the diagram even if we parse them as string.

[Prateek-Wayne]

We should show it as a number on the diagram even if we parse them as string.

@AykutSarac
I made it worked :)

If you agree with the input and output from image,I will raise a pr
or let me know any change needed

[AykutSarac]

@Prateek-Wayne good job, its not in the same color as integer though. could you open a pr so I can review and help?

[Prateek-Wayne]

Hi @AykutSarac
Please take a look at my changes.
The solution is not robust(workaround) and may introduce other issues, so I am marking this as a draft for now.
#476
Please let me know your thoughts.