-
I have a weird issue that I have not really been able to reproduce with a minimal example. I have a fairly simple targets setup. This is my library(targets)
library(tarchetypes)
source("R/functions.R")
options(tidyverse.quiet = TRUE)
tar_option_set(packages = c("scales", "tidyverse", "hrbrthemes"))
list(
# baseline file -----------
tar_target(
baseline_file,
"../outputs/xyz.csv",
format = "file"
),
tar_target(
baseline,
read_experiments(baseline_file),
format = "feather"
),
tar_target(
baseline_selection,
select_baseline(baseline),
format = "feather"
),
tar_render(baseline_report, "01-analyse-baseline.qmd")
) This "works" but obviously does not create a quarto styled doc but HTML in the style of RMarkdown. If I replace the last line with Subsequent changes to the report are not being picked up, however: the pipeline runs and finishes, but the document stays how it is.
Which baffles me, since this is the file that I'm trying to create - how can it be required? It might be that I'm not using the package correctly, but this is at least how I'm working with targets and RMarkdown files. Any pointers on how to debug this further would be greatly appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Sorry, I don't think I can be much help without a reproducible example I can run. All I can really say is that it's a good idea to try to reproduce the error outside
I strongly suspect the error message "paths missing files: 01-analyse-baseline.html" comes from the fact that |
Beta Was this translation helpful? Give feedback.
-
The issue was resolved by loading packages at the top of the quarto document, instead of assuming that |
Beta Was this translation helpful? Give feedback.
The issue was resolved by loading packages at the top of the quarto document, instead of assuming that
targets::tar_option_set
would do this.