quarto-dev / quarto-dev/quarto

VSCode extension: make debugging of quarto documents easier

Open
#275 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

I have recently switched to VSCode and I must say I like it, but there are some small things which are not as user friendly as in RStudio when working with Quarto documents (which I am doing a lot!).

These are in no particular order:

  • when executing a code block, it is in case of pa parametrised quarto document necessary to load the parameter. I can do this by using params <- rmarkdown::yaml_front_matter('$TM_FILEPATH') in a snippet to insert this wherever I need it (mainly in the setup code cell. It would be nice to have this done automatically when running a code cell or by a keyboard shortcut.

  • Before running an arbitrary code cell, I often have to run the setup cell to load packages, setup folders, etc. So I move up in the document, execute the setup cell, and move back again to where I was working. In my case I had to do this regularly, as my R session crashed... It would be great, to have a shortcut to execute the setup cell (or any other one actually) or, done automatically if a code cell is run which is not the setup cell.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by locating the VSCode extension's code-cell execution path and its handling of Quarto setup cells and parameters. Done means providing a clear way to load parameters and run the setup cell before an arbitrary cell, with behavior verified for the described workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.