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
[RefObject] cannot be extended with additional properties and any properties added SHALL be ignored.
Right now, this change causes any additional fields, like title and description in this case, to be lost by tooling, e.g. as described in swagger-api/swagger-parser#2036 (comment).
The text was updated successfully, but these errors were encountered:
The schema is somewhat of a special case object in OpenAPI 3.1 since it is now essentially just JSON Schema draft 2020-12 and the RefObject limitation no longer applies. See the fixed fields for components [1]. Schema does not allow a "Reference Object" like the others because it is now JSON Schema.
Thanks for the clarification! Good to know, As I understand, this means that the 3.1 schema is valid and fields like title or description should not be lost. In that case, this seems to just be a bug in swagger-parser. I'll close this issue then in favor of swagger-api/swagger-parser#2036
I have the following model:
Starting with smallrye-open-api 4.0 (I tested 4.0.4), this produces the following yaml:
The OpenAPI generated with
smallrye-open-api-core:jar:3.13.0
was this:The latter looks like a well-formed OpenAPI to me. However, the former appears to violate the OpenAPI 3.1 spec, see swagger-api/swagger-parser#2036 (comment).
Right now, this change causes any additional fields, like
title
anddescription
in this case, to be lost by tooling, e.g. as described in swagger-api/swagger-parser#2036 (comment).The text was updated successfully, but these errors were encountered: