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
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
I found a solution on this one and I will open a PR soon. It is worth noting that the only reason the sf-integer is shown correctly it is because we have wrongly set its base type to string. Which means that the base type is basically set to "integer, string" instead of ["integer", "string"].
You can check it also by the produced JSON: https://spec.openapis.org/api/format.json
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: