quarto-dev / quarto-dev/quarto-cli
keep-ipynb notebook with cell magics and yaml options can't be executed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
e.g.
```{python}
#| output: asis
%%javascript
// some JS code
```
This is because cell magics need to be the first line of the cell.
Note that the keep-ipynb feature is really designed for debugging rather than for producing a final notebook for distribution (e.g. markdown constructs like citations and crossrefs are not resolved in this version). We should either resolve this or make it more clear in the documentation that keep-ipynb is for debugging intermediate representations (we could even change the filename to make this more clear).
Contributor guide
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 with the keep-ipynb feature and reproduce the supplied notebook containing YAML cell options and a JavaScript cell magic. Determine whether the generated notebook can execute with the cell magic first, or whether the documentation must clearly describe keep-ipynb as an intermediate debugging representation. Done means the behavior is resolved or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jupyter-notebook
- Domain
- documentation, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100