PowerShell / PowerShell/vscode-powershell
Support stopAtEntry
Open
Nobody has claimed this yet.
Area-Debugging
Hackathon
Issue-Enhancement
Up for Grabs
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Should we support something like this for debugging:
Stop at Entry
Setting the stopAtEntry flag will cause the debugger to break immediately on the entry point to the application. This allows you to start stepping through your code without setting breakpoints.
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 files, tests, or entry points are named in the issue. Start by reviewing the repository's existing debugging support and how the VS Code extension launches a debugging session. Done means the stopAtEntry flag is supported and the debugger breaks at the application's entry point without a manually set breakpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100