Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

_quarto.yml: unknown or misplaced keys under project:/website: are silently ignored (Quarto 1 fails validation)

Abierto
#880 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, yaml

Línea de trabajo

Start by tracing q2 render project configuration loading and the existing Q-1-18 diagnostic for unknown properties, then inspect the schemas for project, website, and other closed top-level blocks. Add validation that reports unknown or misplaced keys with their location; a useful result is diagnostics for the shown tocc and llms-text examples, with the existing format.html.llms-txt case still handled according to its open schema.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Summary

_quarto.yml is not checked for unknown or misplaced keys. A typo under website: or project:, or a key nested under the wrong parent, renders silently with the option having no effect. Quarto 1 fails validation with the property name and location. q2 has the diagnostic for this (Q-1-18 Unknown Property, "closed" schemas) and its doc even lists "a property that belongs to a different block" as a typical cause, but it does not fire for the project config.

How this was found: llms-txt: true placed under format: html: instead of website: produced nothing, no warning, and it took a trip to the docs to see why. (Quarto 1 is silent for that specific placement too, since format.html is open for pandoc metadata; the cases below are the ones where it does speak up.)

Repro

A scaffold (q2 create project website site --no-prompt) with one of these configs:

Unknown and misspelled keys under website:

project:
  type: website
website:
  title: "site"
  tocc: true
  llms-text: true
format:
  html:
    theme: cosmo

Unknown key under project:

project:
  type: website
  tocc: true
website:
  title: "site"
format:
  html:
    theme: cosmo

Known key under the wrong parent

project:
  type: website
website:
  title: "site"
format:
  html:
    theme: cosmo
    llms-txt: true
q2 render site
quarto render site
Config Quarto 1 (99.9.9 dev) q2 0.35.0-nightly.20261021
website.tocc, website.llms-text ERROR: … validation failed. (line 5, columns 3--7) property name tocc is invalid … (line 6) property name llms-text is invalid, with the location website:tocc renders, no output
project.tocc ERROR: … property name tocc is invalid … location project:tocc renders, no output
format.html.llms-txt renders, no output renders, no output

Expected

At least what Quarto 1 does: Q-1-18 for unknown properties under the closed blocks (project, website, and the other top-level blocks that have schemas), as an error or at least a warning. A nice extra that Quarto 1 does not have: when the unknown key is a known key of a sibling block (llms-txt is website.llms-txt), say so in the hint.

Environment

q2 0.35.0-nightly.20261021 (macOS arm64); repo at ad283a2cb. Quarto 1 at 99.9.9 (dev build from quarto-cli).

Lenguaje dominante
Rust
Estrellas
278
Forks
19
Merge medio
20 h 23 min
PR fusionados (30 d)
164

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de quarto-dev/q2

Todos los issues de quarto-dev/q2

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.