quarto-dev / quarto-dev/quarto-cli
Consider support for `class.source` `class.output` `attr.source` `attr.output` equivalent (not only available for knitr cells)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
See discussion and example in https://github.com/quarto-dev/quarto-cli/issues/1581
In short, some knitr option could be useful with other computation engine and this require broader Quarto support
This could maybe even be done using Lua filter in an extension (TBC)
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 by reading the discussion and example in quarto-dev/quarto-cli#1581, then compare the listed knitr options with the behavior of other computation engines. Determine whether equivalent support belongs in Quarto broadly or could be provided by a Lua filter extension; done means the intended options work beyond knitr with a clearly defined scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100