gam2table(): should it be exported?
Closed this issue · 6 comments
R CMD check
reports on:
Undocumented arguments in documentation object 'gam2table'
‘mods’ ‘modnames’
Documented arguments not in \usage in documentation object 'gam2table':
‘x’ ‘xnames’ ‘include_anova_pvals’
While looking at this, I noticed that rtemis:::gam2table()
is documented by not exported;
Lines 1 to 20 in 31cd8eb
Should it be exported?
FWIW, it looks like R CMD check
picks up another gam2table
from one of the dependencies.
Not at this point. I added #' @keywords internal
to both glm2table()
and gam2table()
Got it. So, in recent versions of R (I think >= 4.3.0), R CMD check
now checks all man/ pages, which I think required ditto functions to be exported. I created PR #56 that adds #' @noRd
to this function to fix the check warning that you otherwise gets.
Should I add #' @noRd
to all #' @keywords internal
functions?
I guess that's rOpenSci's recommendation (https://devguide.ropensci.org/building.html)
Before reading roxygen's docs, I thought #' @keywords internal
would stop docs from being rendered, instead of just excluding from documentation index.
Should I add
#' @noRd
to all#' @keywords internal
functions?
I'm pretty sure it's only needed for non-exported functions. Note that #' @keywords internal
has nothing to do with a function being exported or not; it just declares that the function/object should not be listed in the HTML help index.