-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: rogerdigital/smart-explorer
base: 0.5.0
head repository: rogerdigital/smart-explorer
compare: 0.5.1
- 12 commits
- 12 files changed
- 1 contributor
Commits on Jun 23, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 810789e - Browse repository at this point
Copy the full SHA 810789eView commit details -
Merge pull request #52 from rogerdigital/codex/update-readme-demo-gif
Update README demo GIF
Configuration menu - View commit details
-
Copy full SHA for 355bc80 - Browse repository at this point
Copy the full SHA 355bc80View commit details -
chore: sync CLAUDE.md, archive historical plan, remove unused screenshot
- Sync CLAUDE.md code map with AGENTS.md (version 0.5.0, add dropIndex/treeExpansion/revealPath/touchLongPress modules) - Move historical development plan from docs/plans/ to docs/archive/ - Remove unused docs/screenshots/smart-explorer-right-panel.png (no longer referenced)
Configuration menu - View commit details
-
Copy full SHA for cc9054b - Browse repository at this point
Copy the full SHA cc9054bView commit details -
Merge pull request #53 from rogerdigital/chore/repo-cleanup
chore: repo cleanup
Configuration menu - View commit details
-
Copy full SHA for c9f32cf - Browse repository at this point
Copy the full SHA c9f32cfView commit details
Commits on Jun 25, 2026
-
fix: align list view scroll speed with tree view by disabling virtual…
…ization The virtualized list rebuilt its visible-row DOM on every scroll event, which made flat list scrolling move noticeably more content per wheel input than the non-virtualized tree view (perceived as 'too fast'). Raise VIRTUAL_THRESHOLD out of reach so the list renders all rows directly, matching the tree view path and its scroll behavior. The VirtualList code is retained for a future fix that re-enables virtualization without the speed regression.
Configuration menu - View commit details
-
Copy full SHA for ee8d911 - Browse repository at this point
Copy the full SHA ee8d911View commit details -
fix: keep list position stable when entering or exiting inline rename
Entering or exiting inline rename (and background vault-event rebuilds) called renderList, which emptied the container and rebuilt the DOM. Two issues caused the list to jump: 1. scrollTop was restored while the container was still empty, so the browser clamped it to 0 — the list flashed to the top / selected row. 2. input.focus() scrolls the focused row into view by default, fighting the restored position asynchronously. Split renderList into renderListContent + a try/finally wrapper that restores scrollTop only after the new DOM exists (via VirtualList.scrollTo or a direct assignment). Pass { preventScroll: true } to focus so it no longer scrolls. Remove the now-redundant scrollTop save/restore in the manual-reorder handlers, which renderList now owns.Configuration menu - View commit details
-
Copy full SHA for e63e0f4 - Browse repository at this point
Copy the full SHA e63e0f4View commit details -
Merge pull request #54 from rogerdigital/fix/list-scroll-speed-and-re…
…name-position fix: align list scroll speed with tree view and stabilize rename position
Configuration menu - View commit details
-
Copy full SHA for 2312584 - Browse repository at this point
Copy the full SHA 2312584View commit details -
fix: preserve child records and manual order on folder rename/move
Obsidian emits a single rename event for the folder itself when a folder is renamed or moved, not for each child file. The previous handler only updated tree-expansion and selection state, leaving the file index with stale child records and the manual order with stale paths that the next manual-mode render would prune — silently losing the user's sort for the entire moved folder. Add FileIndex.renameFolder to rewrite every record at or under the old path to its new location (path + parentPath), and rewrite matching manualOrder entries via the existing renameNestedPath helper. Added tests covering nested files, record-count preservation, no-op, and shared-name-prefix guards.
Configuration menu - View commit details
-
Copy full SHA for 7d42d39 - Browse repository at this point
Copy the full SHA 7d42d39View commit details -
fix: harden manual order persistence and reject invalid names
Three data-safety improvements bundled (same file): 1. onClose now flushes a pending manual-order save instead of just clearing the debounce timer. Previously a reorder followed by quickly closing the leaf within the 500ms window dropped the save, losing the user's most recent sort on next load. 2. The create handler no longer appends new files to manualOrder inline. That append contradicted initializeManualOrder's reconcile, which places missing files at their seed-sorted position — so ordering depended on whether files were created before or after the last manual session. Reconcile now owns new-file placement consistently. 3. Inline create/rename rejects names containing '/', '\', or '..'. A typed or pasted name with path separators previously created files at unintended nested locations or escaped the target folder.
Configuration menu - View commit details
-
Copy full SHA for 4d88046 - Browse repository at this point
Copy the full SHA 4d88046View commit details -
Merge pull request #55 from rogerdigital/fix/vault-rename-data-integrity
fix: vault rename data integrity, manual order persistence, name validation
Configuration menu - View commit details
-
Copy full SHA for 67492ed - Browse repository at this point
Copy the full SHA 67492edView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7d4d761 - Browse repository at this point
Copy the full SHA 7d4d761View commit details -
Merge pull request #56 from rogerdigital/release/0.5.1
release: 0.5.1
Configuration menu - View commit details
-
Copy full SHA for 69b8a0b - Browse repository at this point
Copy the full SHA 69b8a0bView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.5.0...0.5.1