quarto-dev / quarto-dev/quarto-cli

Author name doesn't render correctly with YAML listing content when using extended author schema

Open
#12,052 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

When using a YAML listing content file, the first two examples render correctly, but the third does not.

Renders correctly:

- title: "Item 1"
  author: Bob Smith

Renders correctly:

- title: "Item 1"
  author: 
    - Bob Smith
    - Anna Smith

Renders author names as [object Object]:

- title: "Item 1"
  author: 
    - name:
        family: Smith
        given: Anna
    - name:
        family: Smith
        given: Bob

The bug is identical to closed issue: https://github.com/quarto-dev/quarto-cli/issues/4881#issue-1630364099

Steps to reproduce

listing.qmd:

---
title: "Listing Example"
listing:
  id: sample-listings
  contents: listing.yaml
  sort: "date desc"
  type: table
---

listing.yaml:

- title: "Item 1"
  author: 
    - name:
        family: Smith
        given: Anna
    - name:
        family: Smith
        given: Bob
Expected behavior

The author list processed and names appear as documented in the Quarto docs.

Actual behavior

The reprex is rendered with author names as [object Object]:

Image
Your environment

OS: macOS 15.2 24C101 arm64
IDE: VSCode 1.96.3

Quarto check output
quarto check
Quarto 1.6.40
[✓] Checking environment information...
      Quarto cache location: /Users/iain/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.4.0: OK
      Dart Sass version 1.70.0: OK
      Deno version 1.46.3: OK
      Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.6.40
      Path: /Applications/quarto/bin

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

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /Library/TeX/texbin
      Version: 2022

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

[✓] Checking Python 3 installation....OK
      Version: 3.10.12 (Conda)
      Path: /opt/homebrew/Caskroom/miniforge/base/bin/python
      Jupyter: 5.7.2
      Kernels: julia-1.8, python3

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

[✓] Checking R installation...........OK
      Version: 4.4.1
      Path: /Library/Frameworks/R.framework/Resources
      LibPaths:
        - /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/library
      knitr: 1.48
      rmarkdown: 2.28

[✓] 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.

Research direction

Start by rendering listing.qmd with listing.yaml using the extended author schema, then compare the output with the simpler author examples in the report. Trace how the listing content's structured author names are processed; done means the family and given names render as documented instead of [object Object].

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.