-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
knitr params specified in project profile ignored #84
Comments
If I add
then render with:
I get the expected output (FALSE). But I'm still not sure how to pass params in a |
Okay, looks like you can render the HTML file and pass params, then serve the Shiny app without rerendering:
then
This seems like an okay workaround, but I'm not sure there is a way to publish to Posit Connect using this method. It seems that once deployed to Posit Connect the HTML file will be rerendered even if you upload the locally rendered HTML file. |
Adding the following to
|
We don't currently support params at project level. See quarto-dev/quarto-cli#864 for current feature request For now, params needs to be defined and set at the document level, and then each document render using command line or default value. it seems you manage to do what you wanted so I'll close this, and you can follow the other issue |
Here is a quarto document that prints out a knitr param value:
Here is a
_quarto.yml
project profile file in the project root directory:I expect
params$val
to be printed out, but instead I get an error:object `params` not found
I also tried specifying Knitr params using the quarto CLI described here:
but I get the same error.
How do I pass kintr params via profiles?
The goal is to list default params in the
_quarto.yml
file and create more profiles like_quarto-profile1.yml
and_quarto-profile2.yml
that can be selectively called to update the default params set in_quarto.yml
.The text was updated successfully, but these errors were encountered: