Repository navigation
fix(app): show global-project sessions in web Home - #46520
SeashoreShi wants to merge 1 commit into
Conversation
07326a1 to
f7a2b8f
Compare
|
Rebased onto latest |
|
Heads up: I opened #50440 for the same issue (#46444) before finding this PR — sorry for the overlap, not trying to duplicate work. Difference: this PR is the smaller change (1 file, +8/−1); mine matches by Happy to consolidate onto whichever you prefer. If you'd rather keep this one, say so and I'll close #50440 and hand over the test file so you can fold it in. If it's easier, I can also put your approach and my test into a single PR. Either way, no hard feelings. |
|
Closing this — it has not seen review since September and I want to keep my contribution queue focused. Thanks for the time; happy to reopen or rework if it is still wanted. |
Issue for this PR
Closes #46444
Type of change
What does this PR do?
The web Home page silently hides sessions created outside any git repo (e.g.
C:\Users\Raphael,C:/,I:/Projetos) when launched from a non-git directory.buildHomeSessionRecordsfilters sessions by matchingsession.directoryagainst the selected project'sprojectDirectories()(= worktree + sandboxes). Sessions outside a git repo belong to theglobalproject, whose worktree is forced to/inproject.tsfromDirectoryand which never accumulates sandboxes — so the session's real directory never matches and it's dropped from the Home list. The CLI doesn't hit this because it lists byproject_id.Fix: keep
global-project sessions visible in the Home filter (theirprojectIDis"global"). The directory-based filter still applies to all git-backed projects; the follow-upprojectForSessionlookup still resolves the correct project for display.Changes:
packages/app/src/pages/home/home-sessions-controller.tsx: skip the directory filter for sessions whoseprojectID === "global".How did you verify your code works?
bun test --conditions=solid ./src/context/global-sync/home-session-index.test.ts): 7 pass, 0 fail.Checklist