We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Related: json-schema-org/json-schema-vocabularies#45
In many places including in IETF standards like JOSE, BigIntegers are represented not only as JSON Strings, but as specifically encoded such: https://tools.ietf.org/html/rfc7518#section-6.3.1
BigIntegers
This also permits hassle-free, cross-platform JSON messaging since IEEE-754 remains an issue in JavaScript.
In fact, even an int64 fails (loses data) using ECMAScript's JSON.parse() since IEEE-754 double precision only provides 53 bits of precision.
int64
JSON.parse()
The text was updated successfully, but these errors were encountered:
This is a duplicate of json-schema-org/json-schema-vocabularies#45. We don't need any convincing on the utility of numbers encoded as strings. As I have stated many times, we just need someone knowledgeable to step up and write a PR. If you are willing to do that, please make a note in json-schema-org/json-schema-vocabularies#45.
Sorry, something went wrong.
No branches or pull requests
Related: json-schema-org/json-schema-vocabularies#45
In many places including in IETF standards like JOSE,
BigIntegers
are represented not only as JSON Strings, but as specifically encoded such:https://tools.ietf.org/html/rfc7518#section-6.3.1
This also permits hassle-free, cross-platform JSON messaging since IEEE-754 remains an issue in JavaScript.
In fact, even an
int64
fails (loses data) using ECMAScript'sJSON.parse()
since IEEE-754 double precision only provides 53 bits of precision.The text was updated successfully, but these errors were encountered: