-
Notifications
You must be signed in to change notification settings - Fork 334
SEP-51: XDR-JSON Specification #1699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ecosystem/sep-XDRJSON.md
Outdated
_Note: JavaScript runtime implementations of JSON do not support numbers that | ||
require more than 53-bits. JavaScript applications should use a JSON decoder | ||
supporting 64-bit numbers in JSON numbrs. JSON decoders in other languages do | ||
not typically have this constraint and support numbers up to 64-bits._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edit: Moving to discussion, my bad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, that's why we have this open issue to change it, and also change the presentation of the 128 and 256 bit integer types too:
This PR captures the existing XDR-JSON format which has this wart unfortunately.
Fwiw while that issue has been open for a while, I think we'll prioritise it this year.
No description provided.