fix(web): preserve file tree expansion state across reloads

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code

[enisze]

Problem

Reloading/refreshing the files in the file browser auto-expanded the file tree, wiping out the user's current expand/collapse state.

Root cause

The effect that syncs file data into the tree guarded with a reference-equality check (previousTreePathsRef.current === treePaths). A refresh (useAtomRefresh) yields a brand-new entries array even when the file list is identical, so treePaths was always a new reference. The guard never short-circuited, so model.resetPaths(treePaths) ran on every reload — and resetPaths re-applies initialExpansion: 1, re-expanding collapsed folders and resetting the collapse toggle.

Fix

Compare treePathsby value instead of by reference. When the reloaded paths are identical, the effect updates its refs but skips resetPaths, leaving the tree's expansion state untouched. resetPaths still runs when the file list actually changes (files added/removed/renamed).

🤖 Generated with Claude Code