PowerShell / PowerShell/vscode-powershell
Cabelo de ku de mendingo
Open
Nobody has claimed this yet.
Issue-Bug
Needs: Triage
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all open and closed issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
- If this is a security issue, I have read the security issue reporting guidance.
Summary
Lucas
PowerShell Version
Hzhsuhsxjjd
Visual Studio Code Version
Hhzbhxhxdnz
Extension Version
Bzbssbzbsjsn
Steps to Reproduce
Jzzjsjsjsjsjsj
Visuals
No response
Logs
No response
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
The issue names no files, tests, or usable entry point, and its version, reproduction, and summary fields contain no actionable information. Start by obtaining a concrete description of the extension behavior, valid version details, and reproducible steps; completion cannot be defined until the expected behavior and failure are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 5/100