When importing OpenAPI spec use tags versus paths

[joshuawoodward]

If you import a OpenAPI (swagger) spec file, the collection and folders appear to be grouped by the paths, versus the tags.

In a Swagger UI endpoints are grouped and ordered by the Tags

In Postman the endpoints are grouped and ordered by the paths (just the root)

Ideally postman would look like the following (after I manually edited). This would match the grouping of our documentation (not postman docs) and our swagger UI (playground)

[jgroom33]

+1

[mshimao]

+1

[abhijitkane]

@joshuawoodward @mshimao This was actually a decision we made while working on the Swagger->Postman conversion. A few areas where Postman differs w.r.t tags:

1. Swagger lets you have multiple tags per operation, allowing a request to show up in multiple folders. This is currently forbidden in Postman. We'll need to take a deeper look at our folder/request structure, but I don't see this changing anytime soon.
2. I'm not sure how Swagger would let you define have multiple levels of folders. This is something that Postman supports (even though the Swagger2.0 importer doesn't yet - we'll be updating this soon), and working with just one level of folders is prohibitive for large APIs.

We're working on a tagging system to better mirror what Swagger offers - we'll keep this thread updated with more info.

[jgroom33]

@abhijitkane
An acceptable implementation for the use cases I've encountered would be to use the first tag noted in the request. This would allow people to reorder the tag list for each request to achieve the desired outcome. Though, in the majority of cases I've seen, a request does not contain multiple tags.

[benhamill]

I agree with @jgroom33. We use the tags for organization of endpoints logically in a way that isn't necessarily related to the URLs. Using the first tag would be what I'd expect and is, I'm pretty sure, what other tools that use OpenAPI do (e.g. redoc).

[abhijitkane]

For the OpenAPI3 importer - #3

[smshuja]

ReDoc is using vendor extensions
https://github.com/Rebilly/ReDoc/blob/master/docs/redoc-vendor-extensions.md#x-tagGroups

This seems like a good option.

[a85]

We'll be moving all these issues to importer specific projects. These are open-source plug-ins that Postman maintains so feel free to submit a pull-request and we can look at the behavior. We will be migrating these issues to that tracker soon.

[namtab00]

any progress, anywhere on this one?

[abhijitkane]

@namtab00 We're targetting this as an option for the next release of this module, but including the setting in the Postman app will take a few weeks.

[lrobledo]

@namtab00 Do you mean the code for this feature is already written? I forked the repo to start working on a solution, but I don't want to duplicate work if it's already done and waiting on a release.

[namtab00]

@lrobledo
...I believe your question is for @abhijitkane , I'm just passing by...