microsoft / microsoft/MIEngine
implement progress report for VSCode
Open
Nobody has claimed this yet.
Feature Request
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Contributor guide
No contributing guide indexed for this repository
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 src/DebugEngineHost/HostWaitLoop.cs at lines 19-29, then compare the linked VSCode request with the Debug Adapter Protocol ProgressStart specification. Trace how the wait loop currently behaves and define the expected progress-report lifecycle; done means the requested progress report is emitted in the relevant VSCode debugging flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100