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
I've modified hook_purl in order to have the option purl="comment". With this option, the code is commented in the output script, even when it is evaluated.
I'm just sharing in case you think this is a good idea (see example below) and you want to add this modification in the package.
Below is an example of application that illustrates the reason why I did this modification:
<<response-knitexpand, purl="comment">>=
outResp <- NULL
for (iResponse in seq_len(nResponses)){
outResp <- c(outResp, knit_expand(responseTemplateFile))
}
@
In this chunk, I run knit_expand. Of course I want this code to be evaluated, but I don't want it in the script extracted by hook_purl. However I use purl="comment" instead of purl=FALSE. In this way I get the code as comments in the script. This is helpful to see that the report ran knit_expand at this place.
The text was updated successfully, but these errors were encountered:
Hello knitr developers,
I've modified
hook_purl
in order to have the optionpurl="comment"
. With this option, the code is commented in the output script, even when it is evaluated.I'm just sharing in case you think this is a good idea (see example below) and you want to add this modification in the package.
My code:
Below is an example of application that illustrates the reason why I did this modification:
In this chunk, I run
knit_expand
. Of course I want this code to be evaluated, but I don't want it in the script extracted byhook_purl
. However I usepurl="comment"
instead ofpurl=FALSE
. In this way I get the code as comments in the script. This is helpful to see that the report ranknit_expand
at this place.The text was updated successfully, but these errors were encountered: