-
Notifications
You must be signed in to change notification settings - Fork 37
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
Tags not included from the subsequent swaggers #62
Comments
not sure if i understood this 100%, but yes none of the tags were added into a merged swagger from the tags presented in the header of each swagger json registered in the apis URL, this removes not only the tags but also documentation about these tag (description) from the merged swagger. You still have option to add this manually into config swagger, but than you always have to merge all the changes manually. in combineSchemas method would do this trick but do not know if addtags / renametags will still do that job to manipulate with those "header" tags. if not, modification of addTags / renameTags will be required |
FWIW, this problem exists in OAS 3.x as well (now that -parser supports 3.x). Having to manage tags in the combine.config file is a pain, since I define a set of micro services as separate specifications, and a utility spec for re-usable fragments. I would like to keep the micro service descriptions where it belongs. Also, The same seems to be true with securitySchemes (missing from combined spec). |
Is this the same as the issue I raised more recently? If so, it's fixed in the 1.3.0 release of this library, provided you pass the |
the
may be a separate issue. |
Running the command
with the following configuration
Issue
The "tags" are not getting included from the swagger files under
apis
.The text was updated successfully, but these errors were encountered: