Skip to content

fix(consult): use personal-squad dir in getPersonalSquadRoot() (#590)#615

Closed
tamirdresher wants to merge 1 commit intobradygaster:mainfrom
tamirdresher:fix/personal-squad-root-path
Closed

fix(consult): use personal-squad dir in getPersonalSquadRoot() (#590)#615
tamirdresher wants to merge 1 commit intobradygaster:mainfrom
tamirdresher:fix/personal-squad-root-path

Conversation

@tamirdresher
Copy link
Copy Markdown
Collaborator

Summary

Fixes a path resolution bug where getPersonalSquadRoot() in consult.ts returns the wrong directory, causing squad consult to enter Init Mode even when a personal squad exists.

Root Cause

getPersonalSquadRoot() appends '.squad' to the global squad config path, resolving to an empty path instead of the personal-squad directory.

  • Before (buggy): resolveGlobalSquadPath() + '.squad' -> ~/Library/Application Support/squad/.squad
  • After (fixed): resolveGlobalSquadPath() + 'personal-squad' -> ~/Library/Application Support/squad/personal-squad

This is consistent with resolvePersonalSquadDir() in resolution.ts which correctly uses 'personal-squad'.

Fixes #590

getPersonalSquadRoot() was appending '.squad' to the global squad directory, resolving to an empty folder instead of the actual personal squad at personal-squad/. This caused squad consult to enter Init Mode even when a personal squad exists.

Fixes bradygaster#590
@tamirdresher
Copy link
Copy Markdown
Collaborator Author

Closing — bradygaster has opened #620 which fixes the same issue with a more comprehensive implementation (also fixes shell/index.ts:151 + adds 3 tests via internal review). Deferring to that PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant