Skip to content

Keep internal quarto.* template variables out of the render message#14569

Merged
cderv merged 2 commits into
mainfrom
fix/quarto-variables-console-flood
Jun 3, 2026
Merged

Keep internal quarto.* template variables out of the render message#14569
cderv merged 2 commits into
mainfrom
fix/quarto-variables-console-flood

Conversation

@cderv
Copy link
Copy Markdown
Member

@cderv cderv commented Jun 2, 2026

When rendering any document, the full localized quarto.* template-variable namespace introduced in #14530 is dumped to the console as part of the pandoc ... defaults message — dozens of language-table lines on every render.

The namespace is surfaced through the defaults-file variables: section (so it stays out of yaml_metadata_block writers), and that section is echoed verbatim in the printed defaults message.

pandocDefaultsMessage in src/command/render/defaults.ts now strips the quarto.* namespace, alongside the existing print-only cleaning for patched templates and extension writers. This is display-only: writeDefaultsFile keeps the namespace intact, so template resolution is unaffected, and user-set variables: still print.

Related to #14530

The quarto.* Pandoc template-variable namespace (#14530) carries the
full localized language table, surfaced through the defaults-file
variables: section so it stays out of yaml_metadata_block writers. That
section is still echoed verbatim in the "pandoc ..." defaults message
printed during render, so every render now dumps the entire language
table to the console.

Strip the namespace in pandocDefaultsMessage, alongside the existing
print-only cleaning for patched templates and extension writers. This
is display-only: writeDefaultsFile keeps quarto.* intact, so template
resolution is unaffected. User-set variables still print.
@posit-snyk-bot
Copy link
Copy Markdown
Collaborator

posit-snyk-bot commented Jun 2, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

This smoke test asserted a negative: that verapdf would fail UA-2
validation for an unlabeled captioned figure, because tagpdf placed
<Caption> as a sibling of <Figure> rather than nesting it. Newer
tagpdf/luamml in current TeX Live make verapdf pass UA-2 for the same
document, so the expected failure warning never prints and the test
breaks on CI.

Negate the assertion so the test verifies validation now passes.
Whether the structure tree is genuinely conforming or verapdf simply
stopped flagging it is tracked in #14570.
@cderv cderv merged commit 1de7deb into main Jun 3, 2026
51 checks passed
@cderv cderv deleted the fix/quarto-variables-console-flood branch June 3, 2026 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants