Mahtis Michel

the issue is still persisting in 14.3.6. Inside `node_modules` there is a symlink to the plugin project. After deleting it, the issue is resolved. @AgentEnder is there any way to...

@kael-shipman you could probably just override the component https://github.com/swagger-api/swagger-ui/blob/master/src/core/components/operation-tag.jsx using the plugin api. https://swagger.io/docs/open-source-tools/swagger-ui/customization/plugin-api/ then implement recursive rendering of the operation-tag within the render function of the component.

@kael-shipman for the plugin part I would use the wrapComponents plug point to conditional render either the hirachical operation tag component or the original component.

@kael-shipman let's make this a PR against swagger-ui. I can give you guidance, let's connect to get this going!

> At least in the APIs I work with, this could still be very long. It'd be nice to have some kind of vertical gray line on the left to...

In addition specification wise we are good to implement it. > Tagged operations may be handled differently by tools and libraries. For example, Swagger UI uses tags to group the...

@kael-shipman I don't think we are able to integrate the styling like shown in my comment anyhow I will try to catch up on the PR in the next days...

> Let me preface this by saying this is a dumb question but I'm trying to figure out how so many swagger sites have > "Show/Hide" "List Operations" and "Expand...

@JAdamCain Actualy the difference you are experiencing is due to major version difference of swagger-ui package used.

@tim-lai @webron Could you get the ux team to review this. Also open for a call.