-
Notifications
You must be signed in to change notification settings - Fork 233
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
does roxygen2 support internal S3 methods? #1654
Comments
John Fox also was wondering about this on R-devel, https://stat.ethz.ch/pipermail/r-package-devel/2024q3/011069.html |
See #1592 (comment) |
that comment says from R-3.5 onward, S3 methods should be registered even if they are not exported. How do you do that with roxygen2? the warning says |
Well, that's the thing, the |
right, thanks, that documentation is adequate, I just did not find it until you linked it. 'While S3 methods are regular functions with a special naming scheme, their “export” works a bit differently. S3 methods are exported only in the sense that calling the generic with the appropriate class will call the method; a user can’t directly access the method definition by typing its name. A more technically correctly term would be to say that the method is registered so that the generics can find it.' |
Hi! roxygen2 gives warnings like "S3 method
getStrips.grid
needs @export or @exportS3method" for animint2, animint/animint2#148I see these warnings come from
roxygen2/R/namespace.R
Line 409 in 9652d15
These S3 methods are internal (we don't want to export them). Is there any other way to supprress this warning?
The text was updated successfully, but these errors were encountered: