fix(sessions): use native Pi project directory encoding - #125
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_-/__escape encodingcwdwhen resolving lossy native directory namesFixes #114.
Details
Pi encodes a project path by removing one leading separator, replacing
/,\\, and:with-, and wrapping the result in--. pi-web used a lossless Unix-specific encoding instead, so Pi clients doing current-project discovery could miss sessions created by pi-web.Native encoding is inherently ambiguous for literal hyphens. This change therefore treats the session header's
cwdas authoritative and only decodes the directory name as a fallback. Existing pi-web directories remain readable.Validation
go test ./internal/sessions -count=1go test ./... -count=1go vet ./...gofmtcleangit diff --checkmake buildmake checkreached the frontend suite but encountered unrelated 5-second timeout failures inSessionHeader,SessionSidebarProjects, andSessionTree; those three files passed independently (3 files, 11 tests). No frontend files are changed by this PR.