Improve support for nested postman collection items #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
YOU54F
approved these changes
Jan 15, 2025
|
Released as https://www.nuget.org/packages/Explore.Cli/0.8.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for better management of nested folders within Postman Collections.
Root level requests are now added to an Explore API folder with same name as Explore Space (e.g. Postman collection 'foo' with requests will create Explore Space 'foo' with API folder 'foo' which will contain the request connections).
Nested folders within a collection, will have a name format of
Parent - Child(e.g. foo/bar will create API folder calledfoo - bar, foo/bar/baz will create API folder calledfoo - bar - baz)Fixes: #36