feat: enhance Postman integration with nested folder support and improved documentation handling#9
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Refresh
README.mdto match current behavior: path-based nested Postman folders (pathFolderNesting), short request titles viax-pman-name/x-namevs. longsummaryin Docs, and how sync state + merge removes both new path keys and legacy folder layouts from older releases.Motivation
Users upgrading or switching from tags / flat path grouping to nested folders need a single place that explains the problem, the options, and what happens on merge—without spelunking the source.
What changed
folderStrategy,pathFolderNesting(nestedvsflat), andfolderPathStripPrefixwith a concrete example (/auth/user/admin/create→ Auth → User → Admin).managedFoldersand legacy removal behavior.Test plan
npm testandnpm run lintwere green for code changes in this branch; confirm README renders on GitHub (anchors, tables).Issue: Closes #8