quarto-dev / quarto-dev/quarto-cli
A comment-only `_brand.yml` should trigger a warning but not an error
Open
Beginner friendly
Nobody has claimed this yet.
brand
bug
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
It's useful to have a commented-out brand file for instructional purposes, but quarto doesn't like it. We should fix it.
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 locating the JavaScript validation path for _brand.yml and reproduce the behavior with a file containing only comments. Confirm the change distinguishes a comment-only file from invalid content: it should emit a warning without failing as an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100