Feature request: support for rmarkdown / YAML

[wouteroosterbosch]

As someone who often uses parameterized rmarkdown reports in a complicated directory structure (seperating team coding from reporting, I was a bit surprised to see the YAML not being parsed / taken into account.

While I presume it's possible to work around this by either manually setting parameters (when using ezknitr), or manually moving files (when using rmarkdown), the latter is currently less disruptive to a team's coding flow, imo.

What would need to happen to get the best of both worlds, or is this not a desired path?

[daattali]

This is the case because when ezknitr was developed, YAML in Rmd files did not exist. I first brought up the idea for this package to Yihui over 2 years ago, much before the rmarkdown package had parameterized reports. The end of the README file does briefly touch on this point: when the package started out, parameters was a big advantage, but now that rmd has native support for that, the parameters feature is less important.

The package could certainly be updated to also work with YAML parameters, it just hasn't been done. If you're up for it, you're welcome to submit a PR :)

[asifzubair]

So, does this mean that ezknitr will not parse the yaml header and create a title ? I am currently having this problem and a similar issue was posted on SO. Thanks!

[daattali]

ezknitr does not parse the YAML of an rmd file. I haven't tried using it lately soccer YAML became popular, so I don't know if it will still respect it in some way or not.

[CarolineXGao]

YAML is really useful!! Is it possible to add it on ?

[daattali]

I would be happy to accept a PR for it if you or someone else wants to implement this. Unfortunately I have too many other projects that I need to support for free and don't think I'll have time to work on this.

…

On Tue, May 21, 2019, 04:54 Caroline Gao ***@***.*** wrote: YAML is really useful!! Is it possible to add it on ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=AAHIQFHJSH626WYNZK6S6ITPWOTE3A5CNFSM4DCVYGSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV3CJRA#issuecomment-494281924>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHIQFCRIE6I3SGHNM7MZSTPWOTE3ANCNFSM4DCVYGSA> .

[psychelzh]

Thanks for this package. Current workaround (or even a better solution) is to add this line to your setup chunk of "Rmd" file:

knitr::opts_knit$set(root.dir = here::here())

This will allow you to handle the working directory issue by using knitr package only. Because here::here() will find where your R project is and root.dir option will set that as your working directory.