You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose that if we do not allow any number range, then we note in the README what the limitation on integer and double values are as well as link to the RFC : https://tools.ietf.org/html/rfc7159
The text was updated successfully, but these errors were encountered:
see #157 for discussion.
Neither http://json.org, nor this projects README references the RFC that allows limitations on numeric values. JSON.org references ECMA-404 The JSON Data Interchange Standard which leave the numbers open to exact values.
I propose that if we do not allow any number range, then we note in the README what the limitation on integer and double values are as well as link to the RFC : https://tools.ietf.org/html/rfc7159
The text was updated successfully, but these errors were encountered: