Zhian N. Kamvar

I just found a fun wrinkle: R chunk options that contain backticks cannot be parsed by {commonmark}, and thus {tinkr}: ```` r test writeLines() ```` #> #> #> #> #>...

Add support for chunk options via knitr 1.35

3

So, {knitr} had an exciting release this week that [introduced chunk options inside code blocks](https://github.com/yihui/knitr/releases/tag/v1.35) (which supports quarto documents). It would be a good idea for us to implement this...

should there be an example / test of "apply all possible protections" _Originally posted by @maelle in https://github.com/ropensci/tinkr/pull/78#discussion_r977248869_

protect_curly() introduces extra newlines

1

I believe it's because of the ``: https://github.com/ropensci/tinkr/pull/76/files/3e133e5f6e6b35befef6d8fad20df6d87f8ad549?w=0#r973214227. I guess I was wrong in calling it benign -_- _Originally posted by @zkamvar in https://github.com/ropensci/tinkr/pull/76#discussion_r975376098_

This is a draft to fix #61. It contains a test that confirms the failure at this point, but this will allow me to confirm when it ceases to fail.

Namespace vignette

1

This will address #48. Here is the rendered version via `knitr::purl()` and `reprex::reprex()` Draft of vingette text (updated 2021-05-28) ``` r library("tinkr") library("magrittr") library("commonmark") library("xml2") library("xslt") library("purrr") #> #> Attaching...

Apparently our stylesheet transforms bare links to markdown-style links, using the link itself as the title: ``` r f bare link: [https://example.com](https://example.com) #> bracketed link: [https://example.com](https://example.com) ``` Created on 2021-10-18...

Why do code blocks need a newline at the end?

2

Not a bug, but there's a condition where code blocks need a newline at the end for the last line to be processed by the stylesheet. If anyone has any...

Add helper functions for adding/extracting features

3

Is it worthwhile to add helper functions for adding or extracting nodes? There is an issue around namespaces, which can be tricky. Things I think could be on the docket...

Add `replace()` method for yarn object

1

> Now I wonder whether we still need to use _replacement_ instead of adding. :thinking: > > _Originally posted by @maelle in https://github.com/ropensci/tinkr/issues/37#issuecomment-825418636_ At the moment, we have an `add_md()`...