Pages with categories request listings.json, which 404s when the site has no listing

Aberta
#15,228 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
Meio dia
Facilidade para iniciantes
68/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
javascript, typescript
Domínio
frontend, web-dev

Direção de pesquisa

Start with findAndActivateCategories() in quarto.js and updateGlobalListingIndex() in src/project/types/website/listing/website-listing-index.ts; compare the website and standalone rendering paths described in the issue. Check how the script determines whether listings are available and how the index is written. Done means pages with categories and no listings make no failing listings.json request in either case.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement listings
I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

When a page has categories in its title block, quarto.js fetches listings.json to turn the categories into links to a listing (findAndActivateCategories()).
If no listing exists, that file is not there, so every such page makes a request that returns 404 and logs an error in the browser console.
Rendering is not affected, because the script only reads the response when the status is 200.

This happens in two places:

  • A website with no listing page. updateGlobalListingIndex() in src/project/types/website/listing/website-listing-index.ts only writes listings.json when listingPaths.length > 0.
  • A standalone HTML document with categories. The fetch runs here as well, against listings.json next to the document.

For websites, writing listings.json every time (as [] when there are no listings) would remove the 404.
The standalone case would need the script to know whether listings exist before it fetches.

This is mostly cosmetic.

Steps to reproduce

A website with no listing:

# _quarto.yml
project:
  type: website

website:
  title: "Repro"
---
title: "Home"
categories: [one, two]
---

A page with categories, in a website with no listing.

A standalone document:

---
title: "Standalone"
categories: [one, two]
format: html
---

A standalone document with categories.

Render each one, serve the output over HTTP, open the page and look at the network panel and the console.

Actual behavior

Both pages request listings.json, get a 404, and log Failed to load resource: the server responded with a status of 404 (Not Found) in the console.

Expected behavior

No request for listings.json when there is no listing to link to, and no console error.

Your environment
  • OS: macOS 27.0.1.
  • Browser: Chromium (Brave), headless.
Quarto check output
Quarto 99.9.9
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.10.0: OK
      Dart Sass version 1.101.0: OK
      Deno version 2.9.8: OK
      Typst version 0.15.1: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 99.9.9
      commit: 6f81421488bde28d87cee51c9988e666bc09f7be
Linguagem predominante
JavaScript
Estrelas
6.1k
Forks
476
Merge médio
17h 7min
PRs com merge (30d)
112

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de quarto-dev/quarto-cli

Todas as issues de quarto-dev/quarto-cli

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.