quarto-dev / quarto-dev/quarto-cli
completion changes for execution options
Open
@cscheid is already working on this.
Since Sep 25, 2024.
enhancement
yaml-validation
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Execution options are current handled inconsistently. They can be declared either inside or outside an execute key, and they can appear in different contexts.
Outside execute:
| context | honored | validated | completed |
|---|---|---|---|
| top-level in project configuration | yes | yes | no |
| inside specific formats in project configuration | yes | yes | no |
| top-level in document configuration | yes | yes | no |
| inside specific formats in document configuration | yes | yes | no |
inside code cells with the comment-pipe syntax (#| echo: false, etc) |
yes | yes | yes |
Inside execute:
| context | honored | validated | completed |
|---|---|---|---|
| top-level in project configuration | yes | yes | yes |
| inside specific formats in project configuration | yes | no | no |
| top-level in document configuration | yes | yes | yes |
| inside specific formats in document configuration | yes | no | no |
inside code cells with the comment-pipe syntax (#| echo: false, etc) |
NA | NA | NA |
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.
Assessment
This issue has not been assessed yet.