PowerShell / PowerShell/PowerShellEditorServices
Completions of paths containing "portable" variables should not be resolved to an absolute path
Open
Nobody has claimed this yet.
Area-IntelliSense
Issue-Enhancement
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
See the following issue for more details:
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 with the linked PowerShell/vscode-powershell issue 67, since this issue provides no local files, tests, or entry points. Trace how path completions are resolved and determine the expected behavior for paths containing portable variables; completion results should preserve those variables instead of becoming absolute paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100