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
I'm currently using very outdated library v1.1.1-0.20190620131940-98aa997b1687, and I want to upgrade to latest, but I was really surprised when the swagger validate shows much more warnings with new version.
Thank you for providing the example test.
The lame excuse for current behaviour is that the code base had many contributions that have not been reviewed that carefully. I will have a look at this case to see where the flow is off.
no worries, it is not something major, just some warnings, that can be avoided. You know what I think, maybe we can add a supporting for allOf (it is par of v2) for such cases
so instead of including all fields from Parent, we can create Parent definition and then create Child with allOf: [{$ref: Parent}, {...Child...}]
I'm currently using very outdated library
v1.1.1-0.20190620131940-98aa997b1687
, and I want to upgrade to latest, but I was really surprised when theswagger validate
shows much more warnings with new version.Here is an example of two structs:
with
v1.1.1
it generates just one definition:but
v2.6.1
generates two definitions:and the
swagger validate
shows a warning:It would be great if you can exclude fix the issue.
Here is the test case:
The text was updated successfully, but these errors were encountered: