You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for the amazing CLI and wrapper package for R. I just tried to pass some logical parameters (TRUE/FALSE) from a render.R script to quarto and they got coverted to "yes" and "no". The problem itself and a possible solutions is mentioned in this stackoverflow post:
Since quarto-r is only a wrapper to the CLI I assume that it is not possible to pass booleans from R via YAML to quarto CLI. Would it be feasabile to put somewhere a hint in the documentation that booleans are being converted to a character string?
The text was updated successfully, but these errors were encountered:
Thanks for the report. This is indeed an issue because Quarto follow YAML 1.2 spec with no support for yes/no and yaml R package used by this package is following 1.1 spec with yes/no support for boolean.
Hi there,
thanks for the amazing CLI and wrapper package for R. I just tried to pass some logical parameters (TRUE/FALSE) from a render.R script to quarto and they got coverted to "yes" and "no". The problem itself and a possible solutions is mentioned in this stackoverflow post:
https://stackoverflow.com/questions/73571919/how-to-pass-logical-parameters-with-the-quarto-r-package-to-the-knitr-chunk-opti
Since quarto-r is only a wrapper to the CLI I assume that it is not possible to pass booleans from R via YAML to quarto CLI. Would it be feasabile to put somewhere a hint in the documentation that booleans are being converted to a character string?
The text was updated successfully, but these errors were encountered: