PowerShell / PowerShell/vscode-powershell
Debug Support for Any Exceptions and Uncaught Exceptions
Open
Nobody has claimed this yet.
Area-Debugging
Issue-Enhancement
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Is it possible to debug support to enable break points for: Any Exceptions or Uncaught Exceptions?
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
No implementation files, tests, or entry points are named. Start by locating the TypeScript debug implementation for the VS Code PowerShell extension and review how it handles exception breakpoints. Done means supporting both Any Exceptions and Uncaught Exceptions in the debugger, with behavior matching the VS Code breakpoint options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100