-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Think about methods for generics in suggested packages #1202
Comments
Need to standardise and/or document hack to load packages before |
There is
now. Isn't that good? |
I know I tried that for dtplyr and I'm pretty sure it didn't work. |
Is that because you need to attach the package? I am fairly sure that the loading works. |
Yeah, that's it. |
We can attach |
Yeah, that should be relatively harmless I'd think. |
The original goal of the packages field was to load packages that provided other roclets, but it doesn't seem like attaching these packages will cause harm and creating another field seems like overkill. |
e.g. https://dbplyr.tidyverse.org/reference/pivot_longer.tbl_lazy.html — the tidyr methods look different to the others because (as far as roxygen2 knows), they're not actually methods.
The text was updated successfully, but these errors were encountered: