microsoft / microsoft/vscode-mock-debug
"Inline" / "Server" / "namedPipeServer" have no access to Source locations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 358
- Forks
- 200
- Avg merge
- 24d 23h
- Merged PRs (30d)
- 1
Description
When trying to test & debug Mock Debug in any mode except "external", stackFrameRequests (running in mockDebug.ts) make no attempt to return the Source location for any given stackframe, which means no source highlighting & "unkown source"s galore in testing.
Is this intentional? Why not provide an example for retrieving source locations from a debugger + DA running inline? Especially since only the inline mode is ready to fork & debug out-of-the-box, & is the only option for web-extensions, any examples of source location retrieval would be incredibly helpful.
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 in mockDebug.ts at stackFrameRequests and compare how source locations are handled in external mode with the Inline, Server, and namedPipeServer modes. Determine whether the issue calls for an example or a behavior change, then verify that the chosen modes can provide source locations for stack frames and avoid unknown-source results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100