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
with version v3.25.3 our API-definition is breaking. I did some line-by-line copy-and-pasting, and found out, that it always breaks whenever a definition contains a property named "entries". The error message is not that helpful:
Unable to render this definition
The provided definition does not specify a valid version field.
Please indicate a valid Swagger or OpenAPI version field. Supported version fields are swagger: "2.0" and those that match openapi: 3.0.n (for example, openapi: 3.0.0).
Hallo,
with version v3.25.3 our API-definition is breaking. I did some line-by-line copy-and-pasting, and found out, that it always breaks whenever a definition contains a property named "entries". The error message is not that helpful:
Unable to render this definition
The provided definition does not specify a valid version field.
Please indicate a valid Swagger or OpenAPI version field. Supported version fields are swagger: "2.0" and those that match openapi: 3.0.n (for example, openapi: 3.0.0).
We are using "swagger: '2.0'"
Example of a breaking definition:
definitions:
...
ExampleWsDTO:
type: object
properties:
exampleproperty:
type: number
format: double
entries:
type: array
items:
$ref: '#/definitions/AnotherWsDTO'
anotherproperty:
$ref: '#/definitions/AnotherWsDTO'
...
When I remove the "entries" property, everything works fine. But I cannot actually remove or rename them in our definition.
With v.3.25.2, everything still works fine.
Can you have a look at this, please?
Thank you!
The text was updated successfully, but these errors were encountered: