\dots is being in-properly rendered in html manual

[jangorecki]

When having a function definition in Rd file that uses \dots instead of ...

\usage{
as.myclass(x, \dots)
}

then pkgdown will in-properly rendered html manual
As a result html provide such a chunk of code:

as.myclass(x, …)

where it should be

as.myclass(x, ...)

According to WRE one should use \dots instead of ....

using pkgdown 1.3.0.9100

[jangorecki]

same in examples section, code from examples of form

dcast(DT, \dots ~ v3, value.var = "v4")

produces

dcast(DT, 
#> Error: <text>:31:0: unexpected end of input
#> 29:                  v4 = rnorm(6))
#> 30: dcast(DT, 
#>    ^
# NOT RUN {
…
# }
 ~ v3, value.var = "v4")

the same line processed by utils::make.packages.html looks fine:

dcast(DT, ... ~ v3, value.var = "v4")

[jangorecki]

Thanks for fast fix

[jangorecki]

@hadley Issue for usage in manual and descriptions is resolved, but not the one in examples, reported in second comment.
See https://jangorecki.gitlab.io/data.table/reference/dcast.data.table.html also confirmed locally on current pkgdown@master

[hadley]

Ah that's because of the mix of Rd and R code in the examples; and is probably related to #1087. Fixing it will probably require a rethink of how examples are parsed which I'm not sure I'll have time to do in this release cycle (so you may have to switch to using ..., which I don't think has any downsides.)

[hadley]

Having carefully read https://developer.r-project.org/parseRd.pdf, I'm closing this in favour of #1087 — the key problem is that I'm currently taking an ad-hoc approach to processing the examples, instead of accepting that they're fully capable of containing any Rd text formatting command.