Open ryarazi opened 1 month ago
Thanks for the report.
Our pre-shortcode-filter
are currently processing this syntax. And it seems to happen even for unknown shortcode. Somehow, the attribute names are removed 🤔
Escaping shortcode: https://quarto.org/docs/extensions/shortcodes.html#escaping seems to work here.
```{=markdown}
{{{< vimeo id="146022717" class="my-vimeo-wrapper-class" title="My vimeo video" >}}}
Anyhow, for hugo-md escaping seems to be the key here - though this is a change from what we documented for Hugo https://quarto.org/docs/output-formats/hugo.html#shortcodes
> Note that Hugo [shortcodes](https://gohugo.io/content-management/shortcodes/) and Quarto [shortcodes](https://quarto.org/docs/extensions/shortcodes.html) share the same basic syntax (e.g. {{< var foo >}}). **This is normally not a problem as shortcodes not recognized by Quarto are passed through unmodified to Hugo.**
Not the case anymore.
We should probably at least update the doc, or fix if this is unintended.
It seems we reconstruct the shortcode when unknown, but we are missing the raw_args
names from lst
https://github.com/quarto-dev/quarto-cli/blob/de636882956a7a1c61e2c7893d95be7c2b4310ad/src/resources/filters/customnodes/shortcodes.lua#L227-L230
Definitely a bug we need to fix. I'm surprised about the raw_args
behavior, those should not be touching named args at all.
Bug description
When trying to render quarto .qmd into an .md for a hugo website I get a bug where the names of named arguments are removed from shortcodes.
Steps to reproduce
When I run
quarto render
on:Actual behavior
Instead the resulting file is:
Your environment
OS: Ubuntu 24.04 LTS using Windows WSL
Quarto check output