Preserve literal characters in shared file paths
This commit is contained in:
@@ -267,7 +267,13 @@ reference-cycle, outside-checkout, unavailable-content, and source-tag guards.
|
||||
|
||||
## Issue 8: Preserve literal shared filenames (P2)
|
||||
|
||||
Status: open. Category: unrequested path prohibition.
|
||||
Status: complete. Category: unrequested path prohibition.
|
||||
|
||||
**Completion:** Shared selection preserves literal backslashes in committed Git
|
||||
paths. A Unix regression selects and reads such a file once despite duplicates;
|
||||
traversal, absolute paths, and directories remain invalid selections. Existing
|
||||
literal-metacharacter, missing/default/empty-list, scope, and lazy-input tests
|
||||
pass offline.
|
||||
|
||||
**Evidence:** [`normalizeSharedFile`](../../internal/validation/tree.go) rejects
|
||||
every backslash. On Linux, a committed file named `docs/notice\copy.txt` is a
|
||||
|
||||
Reference in New Issue
Block a user