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
As per the JSON Schema specformat is an open-ended keyword, so you can define your own values.
In this issue #845 (comment) we have discussed creating a format registry either for the OAS or across multiple specs which use JSON Schema.
We're very interested in feedback on what format (!) that registry should take and how people would want to use it.
uint64 would have some interoperability issues with some languages (e.g. Javascript) which map JSON numbers to an internal format which can only support up to 53 bits of integer precision (signed), so some people use type: string in these cases.
Please feel free to continue the discussion on #845
We would like to provide the
type
of integer with additionalformat
types of uint8, uint16, uint32, and uint64.The text was updated successfully, but these errors were encountered: