quarto-dev / quarto-dev/quarto

Lint/check for duplicate chunk titles before render

Open
#1,098 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Migrating https://github.com/posit-dev/positron/issues/15461.

System details:

Positron and OS details:

Positron Version: 2026.08.0 build 331
Code - OSS Version: 1.124.0
Commit: a3a370d4187484ce962794408c76dab702978eaf
Date: 2026-08-05T17:02:37-07:00
Electron: 42.2.0
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Darwin arm64 25.5.0

Session details:

R 4.4.0
Quarto 1.7.32

Describe the issue:

When authoring qmd notebooks, especially for batch rendering/execution on an HPC cluster, a headache is having the job fail because quarto throws an error for a duplicate chunk title. This is hard to notice ahead of time in long qmds with many chunks.

Expected or desired behavior:

I would like a lint / problem check with underline + tooltip warning for duplicate chunk titles (e.g., "#| label: " value) in when editing qmd notebooks.

Thanks for considering!

Contributor guide

No contributing guide indexed for this repository

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

The issue names qmd notebooks and duplicate #| label: values but no files or tests. Start by locating existing notebook lint or problem checks in the Quarto codebase, then determine how to report duplicate labels with an underline and tooltip; done means duplicate chunk titles are detected before rendering and surfaced while editing.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.