Pipes are very functional, unlike data.table. However, their extensive use of
non-standard evaluation a la `subset` or `with` does complicate the package
check process.
As to the actual question, Imports announces that the magrittr package is a
private dependency for your package. Users would h
On 26/07/2019 2:37 a.m., Sigbert Klinke wrote:
Hi,
im my package development I get the following error when checking an
example:
> m <- findMatch('test', x[[1]], FUN='leven(code)') %>% addWave(x[[2]])
Error in findMatch("test", x[[1]], FUN = "leven(code)") %>%
addWave(x[[2]]) :
cou
I'd suggest not to use pipes in package code, as the parser does not
know about them and hence debugging, error messages are more
obfuscated.
Why not use he functional way of R?
For the question: I guess you do not have a corresponding entry in the
NAMESPACE file?
Best,
Uwe
On 26.0
Hi,
im my package development I get the following error when checking an
example:
> m <- findMatch('test', x[[1]], FUN='leven(code)') %>% addWave(x[[2]])
Error in findMatch("test", x[[1]], FUN = "leven(code)") %>%
addWave(x[[2]]) :
could not find function "%>%"
Execution halted
In
