quarto-dev / quarto-dev/quarto

VSCode extension support for markdown cell / code cell in ipynb file

Open
#792 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I develop mainly in ipynb files and I would like to have access to the some quality of life features that are presents when working in a qmd files, namely the auto-completion and snippet insertion. For example when editing a qmd files if I type just sh the extension will suggest to insert a shortcode snippet, or if in a code cell, typing #| will bring up a list of possible valid values.

All of the above is missing when editing on a ipynb files.

I guess the vscode extension would only work on qmd by design, but then stuff like {.callout-note} get rendered correctly in markdown cell of ipynb file, while they do not if the quarto extension is disabled. So the extension is influencing also the ipynb file.

What can I do for extending all the goodness of the quarto extension also to ipynb file?

(The same behavior happen also with Positron, where I did non installed other extension beside the ones it came with it, so I can reasonably exclude any unforeseen conflict with some other extension)

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 or tests are named. Start by reproducing the missing autocomplete and snippet behavior in a VSCode ipynb file, then compare it with qmd editing and the rendering behavior described for markdown cells. Done means the requested Quarto quality-of-life features work in ipynb files without the reported extension conflict.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, 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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.