Hi Sean @seandavi,
On second thought, it seems like it would be more convenient to keep magrittr in the Depends:.
This would avoid all of the library calls in the examples.
Usually, the Depends: field is used if the current package extends the that package.
Seems appropriate to have packages in the Depends: field that are needed for the end user to make effective use of the package. I think magrittr fits this bill.
Hi Sean @seandavi, On second thought, it seems like it would be more convenient to keep
magrittr
in theDepends:
. This would avoid all of thelibrary
calls in the examples. Usually, theDepends:
field is used if the current package extends the that package.Taking a quick look at
Organism.dplyr
, @mtmorgan putsdplyr
in theDepends
field: https://github.com/Bioconductor/Organism.dplyr/blob/master/DESCRIPTION#L16@mtmorgan Thoughts?
Also, the tag should be
@importFrom magrittr "%>%"
, at least that worked for me.Thanks, Marcel