Closed pbchase closed 1 year ago
Is the goal for this to be function or an example script in /report
?
Is the goal for this to be function or an example script in
/report
?
Remind me why we didn't put render_report.R
at ./report/render_report.R
? With the layering feature of containers, I think it would have worked fine. I know I agreed that putting it in the template was a good idea, but having deployed this in a project today, I was wishing it was at ./report/render_report.R
. Instead, I had to copy it to from the redcapcustodian template to ./report
in the project where I was working, release and deploy that. I used the exact script from redcapcustodian. It felt like a pointless operation.
What's more, if we did move it to ./report/render_report.R
and I wanted to revise that "standard" version, then I could copy the file from redcapcustodian to my own project dropping it in exactly the same location, then revise it to meet the needs of that project. That would be a simple, fluid process. It would allow me to deploy with a basic script, discover in using it that I need new features, and replace it with my own modified copy of the REDCapcustodian script.
Hmmm, I can't recall why we did. Looks like placing it in report is better to avoid having to copy. I'll make the changes.
We should add the ability to render Rmds and other script collections. That would require these steps:
render_report.R
from STP to REDCap Custodian.rocker/tidyverse
torocker/verse
to get knitr support.