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
Is your feature request related to a problem? Please describe.
I've got an API I wish to document that has several sub-APIs (e.g. one from a status monitor hosted elsewhere), but I can't create folders deeper than directly under the collection.
Describe the solution you'd like
I'd like to create sub-folders within a collection. For example: api.auroras.live (Collection) => v2 (Folder) => alerts (Folder) => Get all alerts (Request).
It'd be great to allow folders a few levels deep, but within reason of course (e.g. 2-3 levels deep would cover most peoples' needs)
Describe alternatives you've considered
I've considered naming my folders with a hyphen to denote levels, such as v1 - users, v1 - products etc. which would work, but take some careful planning, especially since you can't drag to re-order folders.
Additional context
Might look something like this:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I've got an API I wish to document that has several sub-APIs (e.g. one from a status monitor hosted elsewhere), but I can't create folders deeper than directly under the collection.
Describe the solution you'd like
I'd like to create sub-folders within a collection. For example:
api.auroras.live (Collection)
=>v2 (Folder)
=>alerts (Folder)
=>Get all alerts (Request)
.It'd be great to allow folders a few levels deep, but within reason of course (e.g. 2-3 levels deep would cover most peoples' needs)
Describe alternatives you've considered
I've considered naming my folders with a hyphen to denote levels, such as
v1 - users
,v1 - products
etc. which would work, but take some careful planning, especially since you can't drag to re-order folders.Additional context
Might look something like this:
The text was updated successfully, but these errors were encountered: