swagger-editor
swagger-editor copied to clipboard
"Collapse all" button for operations
That was a really nice feature of the previous editor to collapse all the items on the right side of the editor.
@grosch thanks for the feedback. Can you share a screenshot to point us in the right direction? Just want to make sure we're on the same page.
Well unfortunately I can't because the editor is the new one now, and I always just used the online one.
But basically if you just open up the default online editor, on the right-hand side there's a Schemes dropdown, then a horizontal line, and then all the methods group by tag. There used to be a "Collapse All" type option between that horizontal line and groups of tag dropdown so that I could just collapse them all at once.
There's a link at the top bar of the new editor to use the old editor - http://editor2.swagger.io.
In the middle there is "List all operations". Clicking on that collapses all of the elements (like GET /products). That's what I'm looking to get back into the new editor

This would actually be handled in http://github.com/swagger-api/swagger-ui 😄
We can handle it here though, no worries.
Hi guys,
I agree - this would be a very nice addition to the new editor. The old editor doesn't have the clean "tags" organization that the new one does (granted, it does have the ability to filter on those tags), and it seems odd to deprecate usability/interaction functionality from one product version to the next. Did you have any metrics captured which showed that users weren't using this feature, or did you just guess and remove it assuming it wasn't important?
Hey @DavidMCook, version 3 was actually a ground-up rewrite of Swagger-UI and Swagger-Editor, so this is more of a "didn't reimplement" situation, due to our limited resources.
FYI: If you want to start out with all tags collapsed when the page loads, there is a docExpansion display configuration option that will do that for you today.
We still need this feature!
Please add this feature. It is very difficult while using long API lists