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
{type: number, format: int32} should be a validation error #96
Labels
New passive check
New passive check
Comments
Hey @jayvdb Thanks for the feature suggestion! We're thinking about adding a new passive check that will check for integrity of types, is that what you had in mind? |
Yes |
Great then! We're adding this to our future development plans, thanks for the suggestion :) |
Closed
Hii @jayvdb
I close this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
{type: number, format: int32}
is not ideal OAS 3.0.3, as it defines a format which should be aninteger
, but usestype: number
when thetype: integer
should be used.As it is ambiguous, the validator should emit an error of some sort, as openapi tools are very likely to either ignore either
type
orformat
, or fail when trying to combined the two.An example of a tool which silently ignores the
format
is oxidecomputer/progenitor#266Describe the solution you'd like
Detect
type: number
and a integerformat
, andtype: integer
and a floatformat
.https://github.com/zalando/zally (Kotlin) does detect this as rule
MUST define a format for number and integer types
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: