Visual Debugger Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- vscode
- Domain
- developer-experience, tooling
Research direction
Review the existing VSCode debugging experience for Python scripts and Jupyter notebooks, using the linked VSCode debugging documentation as the behavioral reference. Determine how QMD files could expose breakpoints, stepping, and variable inspection in that interface; done means a QMD analysis can be debugged visually rather than requiring pdb.set_trace().
Written by the indexing model from the issue text.
Description
QMD files currently don't have visual debugging support in the way Python scripts and Jupyter notebooks do. Without this feature, it's still much easier in VSCode to develop analyses using those other options.
In Interactive mode for Python scripts, You can click in the margin to the left of line numbers to set breakpoints. Then you can use Debug Cell to start a debugging session for that code cell. The debugger stops execution at breakpoints and allows you to step through code one line at a time and inspect variables (see Debugging for details.
The closest thing to this that I seem able to achieve is to add the line import pdb; pdb.set_trace() where I want to debug. This triggers a breakpoint where I can interrupt code flow to input commands, but I don't get to benefit from key affordances in VSCode's debugging UI.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
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 quarto-dev/quarto
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
quarto-dev/quarto#1099 ·
-
vscode
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
quarto-dev/quarto#934 · 1 comment · 2 reactions ·
-
vscode
Difficulty 5/5 Over a week Newbie friendliness 42/100
quarto-dev/quarto#1130 ·
-
vscode
Difficulty 3/5 1-2 days Newbie friendliness 68/100
quarto-dev/quarto#1122 ·
-
bug vscode zotero
Difficulty 4/5 3-5 days Newbie friendliness 48/100
quarto-dev/quarto#1119 · 1 comment ·
All issues in quarto-dev/quarto
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·
-
bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·