Generate folders according to the tags in the OAS spec
See original GitHub issueDescription:
When importing an OpenApi 3.0 yaml file with a tags
section, these are ignored. Postman folders seem to be generated based on the first segment of each endpoint’s URL.
Expected Behaviour:
It would be much more convenient if Postman folders derived from a specification’s tags
. (For my use case, anyway. I would be interested to hear other opinions on this.)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Grouping Operations With Tags - Swagger
OAS 3 This guide is for OpenAPI 3.0. If you use OpenAPI 2.0, see our OpenAPI 2.0 ... For example, Swagger UI uses...
Read more >Usage - OpenAPI Generator
Generator for creating a new template set and configuration for Codegen. The output will be based on the language you specify, and includes ......
Read more >Getting started tutorial: Using Stoplight Studio to create an ...
In the sidebar, right-click the Paths folder and select New Path. New path in Stoplight editor · Click the Tags button Stoplight tags...
Read more >Designing REST API with Open API Specification (OAS) v2.0 ...
Arrange the directories accordingly & make sure that you are able to access the API spec file from localhost. Hands-On with OpenAPI ...
Read more >Converting OpenAPI Specs to Postman Collections
API Structure: The OAS spec lists API endpoints according to the path ... strategies to create folders – using operation tags, for example....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
👍 to having an option to allow structuring the collection by tags. Without this our API in Postman isn’t structured the way our docs are presented, making it harder to use.
It’d be really good if the it could use the
x-displayName
vendor extension (used in tools like ReDoc) if it exists. Fall back to the tag name if not.(I’m not willing to pay for Apimatic subscriptions etc)
is there any progress on this?