Back to Signal Feed
CodeTracked since May 19, 2026

Normalize task editor file-tree paths and render from hierarchical children

The PR refactors task-editor file-tree rendering to use a hierarchical `FileNode` model with per-folder `children`, and normalizes local filesystem paths to POSIX-style forms before load, reveal, add/remove, and watch operations. This fixes the root cause where Windows backslash paths were treated as flat IDs (e.g., `src\routes\+page.svelte`), causing duplicated folder/file-like rows in the tree.

FileNodechildrenPOSIX path normalizationLocalFileSystem.relPath

What Happened

  • The PR refactors task-editor file-tree rendering to use a hierarchical `FileNode` model with per-folder `children`, and normalizes local filesystem paths to POSIX-style forms before load, reveal, add/remove, and watch operations. This fixes the root cause where Windows backslash paths were treated as flat IDs (e.g., `src\routes\+page.svelte`), causing duplicated folder/file-like rows in the tree.
  • The PR refactors task-editor file-tree rendering to use a hierarchical `FileNode` model with per-folder `children`, and normalizes local filesystem paths to POSIX-style forms before load, reveal, add/remove, and watch operations. This fixes the root cause where Windows backslash paths were treated as flat IDs (e.g., `src\routes\+page.svelte`), causing duplicated folder/file-like rows in the tree.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced a path-stable, child-walked tree model for the task editor: file nodes now persist hierarchical structure, initial rendering starts from root-only, and nested nodes load on expansion/reveal, preventing backslash-based path variants from producing incorrect duplicate folder/file nodes on Windows.

Why Track This

Why It Matters

Windows users and task-editing teams will see a corrected file tree view (no duplicated folders/files), so expanding folders and selecting files in local projects becomes reliable and less frustrating; continue monitoring path normalization in file-watch/reveal flows for any remaining Windows- and environment-specific edge cases. Technically, the implementation replaces flat parent-index row generation with `rootNodes` traversal over `children`, while normalizing paths at load/store/processing boundaries and preserving existing expansion snapshots, which should also reduce incorrect identity mapping for local file nodes.

Impact

Windows users and task-editing teams will see a corrected file tree view (no duplicated folders/files), so expanding folders and selecting files in local projects becomes reliable and less frustrating; continue monitoring path normalization in file-watch/reveal flows for any remaining Windows- and environment-specific edge cases. Technically, the implementation replaces flat parent-index row generation with `rootNodes` traversal over `children`, while normalizing paths at load/store/processing boundaries and preserving existing expansion snapshots, which should also reduce incorrect identity mapping for local file nodes.

What To Watch Next

  • Watch whether FileNode becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: windows_path_separator_regression, lazy_loading_reveal_consistency.
Open Topic TimelineOpen Technical EventOpen Original Sourcewindows_path_separator_regression / lazy_loading_reveal_consistency / file_watch_event_path_normalization / remaining_path_handling_tests_flaky

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

generalaction/emdash PR #2113: fix(editor): render file tree from normalized children

Fixes duplicated root-level wrappers in the editor file tree by normalizing local paths and deriving visible rows from each node’s children.