Skip to content
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

v3.25.3 breaking on definition containing property "entries" #6021

Closed
jgdiva opened this issue May 20, 2020 · 1 comment
Closed

v3.25.3 breaking on definition containing property "entries" #6021

jgdiva opened this issue May 20, 2020 · 1 comment

Comments

@jgdiva
Copy link

jgdiva commented May 20, 2020

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!

@hkosova
Copy link
Contributor

hkosova commented May 20, 2020

Duplicate of #6016.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants