quarto-dev / quarto-dev/quarto-cli
Quarto project context awareness
Open
@cscheid is already working on this.
Since Jul 13, 2023.
enhancement
inspect
projects
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
It would be nice to have some awareness on Quarto project context at least in quarto check[^1].
For example, quarto check or quarto check project could display:
- presence of
_quarto.ymlwhich defines a project. - presence of
_environment.- A warning could be raised if detected not next to
_quarto.yml.
- A warning could be raised if detected not next to
- presence of
_variables.yml.- A warning could be raised if detected not next to
_quarto.yml.
- A warning could be raised if detected not next to
This also applies to the .local version of those files.
I don't fully know if it is possible, but warnings when "project" features are used without _quarto.yml would also be great (in addition to the current statement in the documentation).
CC @cderv if you think of something else.
[^1]: inspired by the debugging of an issue involving project setup and "auto-detect"/"fallback" method inside Quarto (#6162)
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.