render_site compatibility with Rmd params. #904
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides a solution to #903 and #892 as as a side effect.
@jjallaire I used "output_files" as you suggested. Feel free to suggest changes, although I do not have much more time to devote to this.
Highlights:
render_site
understands theoutput_files
field in the_site.yml
. Ifoutput_files
is missingit uses the Rmd file with the same name. Example of
output_files
field:output_files
feature can be used as well to set as source for an html file a R script that will be spinned:render_site
also understands theautospin
field in_site.yml
. Ifautospin: true
is set,render_site
will render all R scripts spinning them first. (closes Use spin with render_site #892)Tests have been enhanced a bit to cover these features and documentation has been added as well to the
?render_site
man page.I already signed the contribution agreement when I submitted my previous PR (#647)
Comments, patches and merges are very welcome