-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
Regression: fails to invalidate correct schema with an object field named type
#601
Comments
Signed-off-by: Pierre Fenoll <[email protected]>
#602 isn't getting an error about a property named "type". If you share your code it's obviously easier to reproduce your bug! Please do that. Note however that having additional fields sibling to type:
$ref: '#/components/schemas/NamespaceType' # $ref
description: Type of this namespace. # ignored field sibling to $ref From https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.0.md#fixed-fields-19
FYI the biggest change to validation that is part of this range of releases is validation of schema examples and that's the validation error I am getting:
|
I've used Apicurio for creating the OpenAPI specification and that's what it offers. In its workflow it's normal to describe the field itself, more so as the same type might be used in different fields for differing purposes. Looks as if the editor and other validators need to pick this up ... or not. I'll rather stick with the old version as looking at my limited work budget I will rather focus on functionality of the things I build rather than dealing with spec validation in areas where it doesn't produce any indirect value to my employer and our customers, but instead costs. Closing this to reduce the issue load. |
Signed-off-by: Pierre Fenoll <[email protected]>
Signed-off-by: Pierre Fenoll <[email protected]>
Upgrading from v0.94.0 to v0.102.0 I'm seeing a regression where kin-openapi fails to validate a schema that was formerly valid. To back up my claim, https://apitools.dev/swagger-parser/online/ also properly validates my schema. The full schema is https://github.com/thediveo/lxkns/blob/master/api/openapi-spec/lxkns.yaml.
Following is an element where v0.102.0 chokes:
The text was updated successfully, but these errors were encountered: