Possibility to query VSCode UI State
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vscode
Research direction
Start by reviewing the inline debug adapter and the custom-request path described in the issue, then determine whether VS Code exposes the currently selected call-stack frame to the adapter. The issue names no file or test; done would require a clearly defined supported mechanism or an explicit explanation of the boundary.
Written by the indexing model from the issue text.
Description
Not sure if this is the correct place to ask this question - but is it possible for the inline debug adapter to query VSCode for state? For instance, can vscode be queried for information on what stack frame is currently selected from the call stack window, or is this something that is out of this package's control?
For instance, implementing custom requests - a DA might want to know what specific frame is selected to perform some operation on.
- Dominant language
- TypeScript
- Stars
- 306
- Forks
- 90
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 3
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.
More from microsoft/vscode-debugadapter-node
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/vscode-debugadapter-node#325 · 1 comment · 1 reaction ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/vscode-debugadapter-node#307 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-debugadapter-node#286 · 4 comments ·
All issues in microsoft/vscode-debugadapter-node
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·