A comment-only `_brand.yml` should trigger a warning but not an error

Open Beginner friendly
#14,891 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
tooling

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.

Description

brand bug

It's useful to have a commented-out brand file for instructional purposes, but quarto doesn't like it. We should fix it.

Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 7h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.