quarto-dev / quarto-dev/quarto-cli

Support YAML validation for `metadata-files` used in `_quarto.yml`

Open
#8,402 6 comments 0 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Jan 23, 2024.

enhancement websites yaml-validation
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Discussed in https://github.com/quarto-dev/quarto-cli/discussions/8396

Originally posted by anielsen001 January 23, 2024

Description

I'm trying to merge some sidebar information from a metadata-files with an existing _quarto.yml file.

my _quarto.yml looks like this:

project:
  type: website

metadata-files:
  - _sidebar.yml

website:
  title: "Test-sidebar"
  navbar:
    left:
      - href: index.qmd
        text: Home
      - about.qmd
  sidebar:
    style: docked

format:
  html:
    theme: cosmo
    css: styles.css
    toc: true

and the _sidebar.yml file looks like this:

website:
  sidebar:
    - contents:
        - index.qmd
        - about.qmd

when I do this, I get a docked style sidebar, but it's empty. If I comment out the sidebar information in the _quarto.yml, I get the sidebar information from the _sidebar.yml file. The docs indicate that these should merge, but maybe I'm misunderstanding. What's the expected behavior here?

Heres my quarto check out put

Quarto 1.4.533
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.11: OK
      Dart Sass version 1.69.5: OK
      Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.4.533
      Path: /opt/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: (not installed)
      Chromium: (not installed)

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /usr/bin
      Version: 2019

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.8.3
      Path: /home/apn/sw/bin/python3
      Jupyter: 4.10.0
      Kernels: julia-1.8, python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.3.2
      Path: /usr/lib/R
      LibPaths:
        - /home/apn/R/x86_64-pc-linux-gnu-library/4.3
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      knitr: 1.43
      rmarkdown: 2.24

[✓] Checking Knitr engine render......OK

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.