When importing OpenAPI use both tags and paths

[namtab00]

Opening a downstream of #57
see #57 (comment).

When importing an API with tags:

• under a root UI node Folders, create folders from paths
• under a new root UI node Tags, also create a flat list (no hierarchies) of tags, each showing all requests with the current tag

[umeshp7]

@namtab00 Thank you for reaching out, would like to understand the use case a bit more here.
Could you give us an example of what such a collection would look like? Since, as per my understanding, there would be some amount of duplication of requests.
Any particular reason why such behavior is helpful for you?

[namtab00]

Example:

routes

/controller1/action1 - having tags: none
/controller1/action2 - having tags: tag1, tag2, tag3
/controller1/action3 - having tags: tag2

/controller2/action4 - having tags: tag1
/controller2/subpath/action5 - having tags: tag2, tag3
/controller2/action6 - having tags: tag3

post import tree:

/folders
  /controller1
    -action1
    -action2
    -action3
  /controller2
    /subpath
      -action5
    -action4
    -action6
/tags
  /no tag
    -controller1/action1
  /tag1
    -controller1/action2
    -controller2/action4
  /tag2
    -controller1/action2
    -controller1/action3
    -controller2/action5
  /tag3
    -controller1/action2
    -controller2/action5
    -controller2/action6

where requests listed in the /tags subtree are mere pointers, not duplicates, which when clicked move the selection to a node under /folders.

I hope this clears things up a bit..

[abhijitkane]

@namtab00 A workaround for now is importing twice, using the 'Folder strategy' option. At this time, Postman collections don't support references, and duplicate requests don't align with our product roadmap. Closing this issue for now - I don't see this being added to our roadmap anytime in the near future.