microsoft / microsoft/WinAppVSCE
Share canonical path-boundary helpers for XAML services
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 4
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem? Please describe.
The XAML workspace resolver and language server each maintain their own case-insensitive Windows path containment/equality logic. Both are currently tested, but duplicated boundary logic raises the risk that junction, separator, or canonicalization behavior diverges later.
Describe the solution you'd like
Extract a small shared path-boundary utility and use it for project discovery, allowed-root validation, and canonical path equality. Preserve the existing junction-resolution and trusted-root security tests.
Additional context
This is non-blocking follow-up from PR #50's final review; no current boundary bypass was found.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the XAML workspace resolver and language server path-boundary implementations, then run their existing junction-resolution and trusted-root security tests. The work is complete when project discovery, allowed-root validation, and canonical path equality share one utility without changing those security behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100