Report attached and loaded packages in reproducibility table#132
Report attached and loaded packages in reproducibility table#132
Conversation
|
tested locally and it works great for me! here is a screenshot for posterity:
note: the way to resolve the associated issue with the VISCtemplates skeleton so that the packages table can be more than one page is just to add option thanks for tackling this @slager! |
|
associated changes for VISCtemplates: FredHutch/VISCtemplates#329 |
|
@mayerbry do you know if HVTN folks use this function for their reports? if so, we should probably reach out to them. |
|
Tagging @bneradil to weigh in for HVTN |
|
Per Moni, HVTN SRA reports log |
|
While playing around with doing this for one of my PDF outputs where I wanted to include dependencies in a reproducibility table, I noticed a relatively easy/predictable way we may be able to detect and throw the user a warning (which they can always suppress using We could add a warning to this PR if we want to highlight these kinds of cases (even without printing out the local location of every package) |
|
Note from VISCfunctions meeting: Path-checking logic like suggested by @lemireg to go in a separate function, or at least in a separate PR |

Inspired by FredHutch/VISCtemplates#314
Suggested review: Install this branch with
remotes::install_github('FredHutch/VISCfunctions', ref = 'repro_tbl_namespace'), then knit a test report with VISCtemplates. The VISCtemplates skeleton will need an adjustment to allow a packages table to carry over onto a second page if needed.