PRQL code blocks are not rendered correctly with Quarto CLI 1.3 (preview) about prqlc-r HOT 5 CLOSED

Yes you can do that (changing the options$engine) in your engine so that it is picked by Quarto 1.3.

In next version, the lang option will be respected.

from prqlc-r.

I am wondering if I need to add a test to check the rendering results by Quarto.
As Quarto is not an R package and would require an additional step when running on GHA.

There is also the issue of whether the Quarto R package should be added as a dependency......

from prqlc-r.

@cderv Thanks for your comment!
Does #110 look good?

from prqlc-r.

There is also the issue of whether the Quarto R package should be added as a dependency......

IMO you need only to add it (as Suggests) if you want to be thorough while adding a tests for Quarto in testthat while using skip_on_cran() and skip_if_not_installed(), and do snapshot test with markdown output.

Otherwise you could have a specific workflow that do a check without being a tests in R for example and in that case no need to add as a dependency, and no need to run very frequently your test.

By experience, hard to test everything that are output features. We'll check the knitr handling anyway.

from prqlc-r.

Otherwise you could have a specific workflow that do a check without being a tests in R for example and in that case no need to add as a dependency, and no need to run very frequently your test.

Indeed, this might be more appropriate here.
Since Quarto is updated frequently (thanks!), it seems to make sense to periodically run a test on GHA with installing the binary package prqlr from RSPM or R-universe and check the output.

from prqlc-r.