Fix: preserve Postman folder hierarchy during v2.1 import (#879) #980
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.
Summary
Fixes #879. This update preserves the folder hierarchy when importing Postman v2.1 collections by including the folder path in the request name (e.g.,
Users/Auth/Logininstead of justLogin).Problem
Previously, when a collection with nested folders was imported, all requests were placed at the root level. This removed context, made organization harder, and broke the structure users set up in Postman.
Solution
The logic in
postman_utils.darthas been updated so that:/Key Changes
folderPathparameter to both parsing functionsUsers/Create User)Testing