more complete output format dependency detection
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
We introduced detection of output format packages here:
https://github.com/rstudio/packrat/pull/280/files
A couple more things need to be done to make this airtight:
- All output formats that the Rmd could be rendered to need to be inspected (rather than just the default one). This will be possible in a future version of rmarkdown via the new
all_output_formatsfunction: https://github.com/rstudio/rmarkdown/commit/4f36bc0bd2b59343b7c80c0a79103b92b2ca97b7 - There is technically a chance that a custom site generator defined in another package could be referenced in the "site" metadata field (it typically just has "site: true" and uses the default generator or one defined by it's output format however it's possible to pass an arbitrary function here).
We expect that the cases where #1 and #2 are required to correctly detect the dependencies will be extremely rare or non-existent so this isn't urgent.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the files changed in pull request #280 and the referenced rmarkdown all_output_formats function. Trace how Rmd output formats and the site metadata field are currently inspected. Done means dependency detection covers every available output format and the possible custom site generator case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100