We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Swagger parser doesn't parse correctly many levels of references when in the second reference are an object that is referencing another file
Imagine this scenario:
` Main.yaml:
Mail: type: object properties: message: $ref: "../files/Definitions.yaml#/definitions/Message"
Definitions.yaml:
Message: type: object properties: content: type: object properties: contentMessage: $ref: "../files/others.yaml#/Content"
Others.yaml:
Content: type: object properties: text: type: string `
In this scenario swagger creates a POJO (ContentMessage) withou any properties and dont create the last object (Content)
I added some code to consider this situation and i will do a pull request.
The text was updated successfully, but these errors were encountered:
Issue swagger-api#318 and swagger-api#319
cbaefb3
No branches or pull requests
Swagger parser doesn't parse correctly many levels of references when in the second reference are an object that is referencing another file
Imagine this scenario:
`
Main.yaml:
Mail:
type: object
properties:
message:
$ref: "../files/Definitions.yaml#/definitions/Message"
Definitions.yaml:
Message:
type: object
properties:
content:
type: object
properties:
contentMessage:
$ref: "../files/others.yaml#/Content"
Others.yaml:
Content:
type: object
properties:
text:
type: string
`
In this scenario swagger creates a POJO (ContentMessage) withou any properties and dont create the last object (Content)
I added some code to consider this situation and i will do a pull request.
The text was updated successfully, but these errors were encountered: