Add hugo-md to pandoc-all in format-aliases.yml

Open
#14,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with format-aliases.yml and compare the existing dashboard synthesized-format entry. Then inspect src/resources/extensions/quarto/hugo/_extension.yml and quarto-web's tools/reference.ts to resolve whether hugo or hugo-md is canonical. Done means the generated hugo.json contains the expected format options without the workaround.

Written by the indexing model from the issue text.

Description

bug hugo markdown

The hugo-md format is defined as a Quarto extension at src/resources/extensions/quarto/hugo/_extension.yml (based on md with variant: gfm+yaml_metadata_block+definition_lists+smart), but it is not listed in pandoc-all in format-aliases.yml.

This causes quarto-web's tools/reference.ts to produce an empty hugo.json for the format reference page. The script derives format names from .qmd filenames and checks each option's resolved format list against pandoc-all. Since hugo / hugo-md is not in that list, no options match.

The dashboard format was handled by adding it as a synthesized format in pandoc-all. The same approach would work for hugo-md.

There is also a naming mismatch to consider: the extension defines the format as hugo-md, but the quarto-web reference page uses hugo.qmd (deriving the name hugo). The upstream fix should clarify which name should be canonical.

quarto-web has a workaround (mapping hugo to gfm for option lookup) but the proper fix belongs here.

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

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.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.