quarto-dev / quarto-dev/quarto-cli

Epic: Error messages + linting

Open
#8,698 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

epic
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

We could spend some time improving our error messages. (This statement is always true, but there are a number of specific things we could focus on).

Validation

Linting

See Mine's framing here: messages as a call to attention, warnings as a call to action.

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.

Research direction

Start by reviewing the linked error-message, validation, and linting issues, including the checked item #10537 and the referenced discussion on messages and warnings. The epic is complete when its selected child issues have been resolved and the checklist reflects their status.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.