create subfolders in a collection

[yehosef]

We have several APIs we're working with, each have many many resources and endpoints.

Generally how I would like to organize it is by resource, but sometimes the resource I'm getting is actually a part of another resource - example: POST /comments GET /comments GET /comments/ GET /comments//likes DELETE /comments//likes PUT /comments//likes

then I have GET /member//comments GET /member//comments/likes GET /post//comments GET /post//comments/likes

etc. This is just a simple example, - but it can go on and get more complicated.

It would be great if I could make a folder under [comments] so I could also have a [comments][member] and a [comments][post] etc.

I think for now adding another level would be sufficient.. I can understand how adding infinite levels would be difficult to support and probably not so in demand. If you wanted to be able support infinite levels, you might think about a UX similar to workflowy where you can "zoom" in - where the next level in becomes the top level and there are bread crumbs at the top to see where you are. - this would be amazing.

[sunshineo]

1 level folder is supported, this should be closed. But really need multiple level of folders / nested folders.

[yehosef]

I'm specifically asking for more than one level, how is it that this should be closed?

[sunshineo]

@yehosef I read it wrong but you are not good at wording things either. You should have "multiple" or "nested" or something like that in the title or the body. The picture should help.

[yehosef]

@sunshineo - I'm sorry you're not good at reading english - it's a tricky language ;). Since in a collection you can already create "folders", I'm asking for "subfolders" - which is an additional feature. I'm glad you understand better now.

[sunshineo]

@yehosef Well, keep the pretty pictures coming. With the crappy title you picked from your crappy vocabulary. No one is going to look at it.

[yehosef]

Now for something constructive.

@a85 - the more I use this with multiple collections, the more I think having a "zoomed" view would be really helpful (think workflowy).

I think of a collection representing a particular API (eg, twitter, github, etc). I want to mention two things:

1) When I'm working on a particular API, it's not common that I also need easy access to other collections/API. If I did my preference would be to handle this in multiple windows (if chrome apps support it) or tabs.

2) it's common for the APIs to be very big and complex (see https://developer.github.com/v3/) and the current structure becomes unwieldy with such a size. It seems the main issues are UX. You could make it so you can even expand a single collection from the main collection list and to see a collection you click on it to "zoom in" to a single collection view. The single collection view would use the two visual levels that are currently visible to represent the folders, subfolders and endpoints. the only (subtle) difference is that you cannot current put an endpoint at the "global" scope, which in my suggested approach would be the root of the collection.

I'm curious if you've heard similar feedback from other users or heard how they handle multiple big APIs/collections. Maybe there is some other approaches or hacks that would work for me.

Thanks

[kevinjalbert]

+1

[collinpeters]

+1

[youranwj]

+1

[deepredsky]

+1

[MarkMurphy]

+1 I agree, I have multiple apis and need to nest folders at least one level deeper

[eappell]

+1

[ppolyzos]

+1

[stramel]

:+1:

[superruzafa]

+1

[defaultbob]

+1

[igostavro]

+1

[gioid]

+1

[yargevad]

+1, subfolder support would be great

[jamesaspence]

+1. I very much want collections with folders, with subfolders inside the folders, etc. etc.

[aelgali]

+1

[mpurdon]

+1

[zappen999]

+1

[adamtickner]

+1

[makison]

+1

[dmitry-fedoseev]

+1

[monkpit]

So how many years does it take to get a response?

[a85]

This is on our immediate roadmap now. We needed to do several things to make this possible. Subfolder support requires changes in the following:

1. Data format for collections
2. Collection runner (How Postman executes collections)
3. Internal data store and syncing
4. Postman UI

We just pushed an update 4.5 on the Mac app that has the new Postman Runtime which takes care of 1 and 2. We are working hard on 3 and 4 now.

[beetlerom]

Just wondering if there is an ETA on this on. I am planning to start a new project and would like to know if I can rely on the new structure possibilities for it.

Thank you!

[koleror]

+1

[ondrejkrpec]

+1

[ghost]

+1

[hkgill]

+1

[mchambaud]

+1

[fredbouchard]

+1

[victor-ponamariov]

+1

[DeividasJackus]

+1

[rammrain]

+1

[SeanStewart37]

+1

[rafael-iop]

+1

[bgarrison25]

+1

[phoenixgao]

+1 Any estimate?

[stwist-timeless]

+1

[Kalzem]

+1

[lthurston]

+1

[monkpit]

Enough "+1"s - you can use the github reaction feature to add a thumbs up, etc to any post without triggering emails to everyone that contain only the text "+1" and lack actual content.

Thanks!

[stramel]

+1 to @monkpit's comment

[kamiwa]

+1

[GMolini]

+1

[corbfon]

+1