fix(plugin-file-tree): fix 2-space indentation parsing for deeply nested tree structures #17
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
Related issues
AI Summary
What changes were made
detectIndentSize()function - Scans all lines to detect whether the tree uses 2-space or 4-space indentation modecalculateIndent()function - Now accepts anindentSizeparameter to correctly calculate indent levels based on the detected modeWhy they were made
The original tree parser had a bug when handling 2-space indented trees with 3 or more nesting levels. For example:
```tree
docs
├── _meta.json
└── guides
├── _meta.json
└── basic
├── introduction.mdx
├── install.mdx
└── plugin-development.md
```
The files under `basic` directory (4 spaces = 2+2) were incorrectly placed as siblings of `basic` instead of children, because the algorithm treated 4 spaces as a single 4-space indent unit rather than two 2-space units.
Implementation details
This PR was written using Vibe Kanban