Ben,
if I recall there were a couple regressions in knitr that broke things, but
since this is only a WARNING it means the check has not been automatically
repeated after knitr update (ERRORs are re-tried nightly). I can kick off
things manually which is likely to remove the WARNING.
Cheers,
S
Since the main problem is that in base-R's function your 'object' is called
'x', you could consider issuing an intermediate version of the package, where
you strongly advise users not to name the first argument and to always name the
remaining arguments. Also, make sure that your examples foll
The problem with that is a call like
sort_by( object = foo, by = bar )
wouldn't be dispatched to the est_table method when foo is an est_table
object, it would give a "argument 'x' is missing" kind of error. It
would be fine for
sort_by( foo, bar )
but would also mess up on
sort_by( f
I have a package, named 'oce' (developed at www.github.com/dankelley/oce and
available through CRAN for over a decade) that uses 'ncdf4' to read some file
types. When I do test builds on the win and mac builders, all is fine. When I
do it with rhub, though, I get an error that ncdf4 cannot be
Thanks a lot for both suggestions! I haven't thought about these
approaches, They may solve my problem without breaking existing code.
I may just keep the original arguments for backward compatibility.
Coincidentally, "object" and "by" have the same meanings as "x" and
"y" in base::sort_by() and so
I haven't thought about this carefully, but shouldn't this mostly work?
sort_by.est_table <- function(x, y = c("op", "lhs", "rhs"),
object = x,
by = y,
op_priority = c("=~", "~", "~~", ":=", "~1", "|", "~*~"),
number_rows = TRUE, ...) {
}
-Deepayan
On Sat, 3 Aug 2024 at 00:1
Thanks to Ivan Krylov and Dirk Eddelbuettel who came to my rescue.
At first I thought that Dirk's suggestion ("the zero-dependency
approach" due to Mark van der Loo) was exactly what I needed. But this
turned out not to work; rhub_check() still failed with a complaint
about needing pdflatex.
I
