-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Format Registry documentation is not accurate / well published #3703
Comments
Looking a bit deeper in gh-page repo , it looks like data is accurate , but it is more a generation issue of the HTML document and of the JSON document that does not leverage the data for instance int64 is correctly described here |
Yes, something is concatenating two type values instead of rendering them as a comma-separated list. |
I found a solution on this one and I will open a PR soon. It is worth noting that the only reason the |
Resolved by @Bellangelo 's PR - I just checked the rendered pages and they look good now. |
Looking on the page here https://spec.openapis.org/registry/format/
as well on the JSON content here https://spec.openapis.org/api/format.json
there are some mistakes in the collumn type
for instance :
decimal A fixed point decimal number of unspecified precision and range stringnumber
should be string, number
for in64 we have an other version
int64 signed 64-bit integer numberstring
only sf integer looks correct
then about the JSON content , to me the given the constrains that a format can apply to multiple base type it should be represented as an array
"base_type": "numberstring" => "base_type": [ "number","string"]
The text was updated successfully, but these errors were encountered: