Open aronatkins opened 5 months ago
I noticed something a bit similar in another setup using a YAML file to set the content. I can't figure out what's the order logic.
EDIT: using the above setup, you get similar behaviour with:
project:
type: website
website:
title: "things"
sidebar:
contents: things
FYI, the documentation states that "auto" means alphabetical order.
https://quarto.org/docs/websites/website-navigation.html#auto-generation
Is this because the filenames for all entries are things/2024-06-11/index.md
and the sorting is using the "basename" to order?
The basename of every file is index.md
, which means that the sort is ambiguous.
When a sidebar is define by a glob like things/*/index.md
, should the entire (relative) filename should be considered when sorting?
Bug description
Given a project with listings having directory structure and titles derived from dates,
contents: auto
incorrectly orders the sidebar contents.Steps to reproduce
Given a directory structure:
The
quarto.yml
The
index.qmd
Each of the
things/YYYY-MM-DD/index.qmd
files looks like:Expected behavior
The sidebar listing order should show a reversed version of the embedded listing table, where titles are listed in ascending order.
Actual behavior
The sidebar listing order is in some other (arbitrary?) order.
Your environment
Tested with Quarto 1.4.549 and Quarto 1.5.24.
Quarto check output