Replies: 2 comments
-
|
This has nothing to do with the R package wrapper. Note that there are other threads discussing the exact same thing, please try to search before opening new discussions. |
Beta Was this translation helpful? Give feedback.
-
Regarding this, please provide details or open a new issue. Regarding using parameters for execution as Pandoc's metadata to be used in document, lua filter or in template, you need to explicit pass them. This is not done automatically. You can pass them all, or some of them. See the latest article in Quarto R 📦 : https://quarto-dev.github.io/quarto-r/articles/dynamic-metadata.html#advanced-use-case-conditional-content-based-on-parameters |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I’m having trouble propagating parameters with quarto. If I update the yaml parameter, the file renders properly but if i call quarto_render() with execute_params() it does not. Reason why I need quarto_render() is that I have to create multiple reports with various parameter sets on the same template.
Here is my example:
test.qmd
typst-show.typ
typst-template.typ
render.R
Also, I observe that if I use inline-code to call parameters within body, it does not render properly. This may be due to typst but in case someone knows how to deal with that, I’d be happy as well.
results from quarto check
Beta Was this translation helpful? Give feedback.
All reactions