Follow strict Rd rules (#7225)

* Follow strict Rd rules

* Also set this in GHA to catch immediately

Author: MichaelChirico

.github/workflows/R-CMD-check.yaml

@@ -36,6 +36,7 @@ jobs:
       R_REMOTES_NO_ERRORS_FROM_WARNINGS: true
       RSPM: ${{ matrix.config.rspm }}
       GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }}
+      _R_CHECK_RD_CHECKRD_MINLEVEL_: -Inf
 
     steps:
       - uses: actions/checkout@v4

man/IDateTime.Rd

@@ -70,13 +70,13 @@ as.IDate(x, \dots)
 \method{as.IDate}{Date}(x, \dots)
 \method{as.Date}{IDate}(x, \dots)
 \method{as.POSIXct}{IDate}(x, tz = "UTC", time = 0, \dots)
-\method{round}{IDate}(x, digits = c("weeks", "months", "quarters","years"), \ldots)
+\method{round}{IDate}(x, digits = c("weeks", "months", "quarters","years"), ...)
 
 as.ITime(x, \dots)
 \method{as.ITime}{default}(x, \dots)
 \method{as.ITime}{POSIXlt}(x, ms = 'truncate', \dots)
-\method{round}{ITime}(x, digits = c("hours", "minutes"), \ldots)
-\method{trunc}{ITime}(x, units = c("hours", "minutes"), \ldots)
+\method{round}{ITime}(x, digits = c("hours", "minutes"), ...)
+\method{trunc}{ITime}(x, units = c("hours", "minutes"), ...)
 
 \method{as.POSIXct}{ITime}(x, tz = "UTC", date = Sys.Date(), \dots)
 \method{as.character}{ITime}(x, \dots)

man/between.Rd

@@ -3,7 +3,7 @@
 \alias{\%between\%}
 \alias{inrange}
 \alias{\%inrange\%}
-\title{ Convenience functions for range subsets. }
+\title{ Convenience functions for range subsets }
 \description{
 Intended for use in \code{i} in \code{[.data.table}.
 

man/like.Rd

@@ -4,7 +4,7 @@
 \alias{\%ilike\%}
 \alias{\%flike\%}
 \alias{\%plike\%}
-\title{ Convenience function for calling grep. }
+\title{ Convenience function for calling grep }
 \description{
   Intended for use in \code{i} in \code{\link[=data.table]{[.data.table}}, i.e., for subsetting/filtering.
 

man/melt.data.table.Rd

@@ -24,10 +24,10 @@ non-measure columns will be assigned to it. If integer, must be positive; see De
 \item{measure.vars}{Measure variables for \code{melt}ing. Can be missing, vector, list, or pattern-based.
 
   \itemize{
-    \item{ When missing, \code{measure.vars} will become all columns outside \code{id.vars}. }
-    \item{ Vector can be \code{integer} (implying column numbers) or \code{character} (column names). }
-    \item{ \code{list} is a generalization of the vector version -- each element of the list (which should be \code{integer} or \code{character} as above) will become a \code{melt}ed column. }
-    \item{ Pattern-based column matching can be achieved with the regular expression-based \code{\link{patterns}} (regex without capture groups; matching column names are used in the \code{variable.name} output column), or \code{\link{measure}} (regex with capture groups; each capture group becomes an output column). }
+    \item When missing, \code{measure.vars} will become all columns outside \code{id.vars}.
+    \item Vector can be \code{integer} (implying column numbers) or \code{character} (column names).
+    \item \code{list} is a generalization of the vector version -- each element of the list (which should be \code{integer} or \code{character} as above) will become a \code{melt}ed column.
+    \item Pattern-based column matching can be achieved with the regular expression-based \code{\link{patterns}} (regex without capture groups; matching column names are used in the \code{variable.name} output column), or \code{\link{measure}} (regex with capture groups; each capture group becomes an output column).
   }
 
     For convenience/clarity in the case of multiple \code{melt}ed columns, resulting column names can be supplied as names to the elements \code{measure.vars} (in the \code{list} and \code{patterns} usages). See also \code{Examples}. }

man/mergelist.Rd

@@ -31,24 +31,24 @@
   The terms \emph{join-to} and \emph{join-from} indicate which in a pair of tables is the "baseline" or "authoritative" source -- this governs the ordering of rows and columns. 
   Whether each refers to the "left" or "right" table of a pair depends on the \code{how} argument:
   \enumerate{
-    \item{ \code{how \%in\% c("left", "semi", "anti")}: \emph{join-to} is \emph{RHS}, \emph{join-from} is \emph{LHS}. }
-    \item{ \code{how \%in\% c("inner", "full", "cross")}: \emph{LHS} and \emph{RHS} tables are treated equally, so that the terms are interchangeable. }
-    \item{ \code{how == "right"}: \emph{join-to} is \emph{LHS}, \emph{join-from} is \emph{RHS}. }
+    \item \code{how \%in\% c("left", "semi", "anti")}: \emph{join-to} is \emph{RHS}, \emph{join-from} is \emph{LHS}.
+    \item \code{how \%in\% c("inner", "full", "cross")}: \emph{LHS} and \emph{RHS} tables are treated equally, so that the terms are interchangeable.
+    \item \code{how == "right"}: \emph{join-to} is \emph{LHS}, \emph{join-from} is \emph{RHS}.
   }
 
   Using \code{mult="error"} will throw an error when multiple rows in \emph{join-to} table match to the row in \emph{join-from} table. It should not be used just to detect duplicates, which might not have matching row, and thus would silently be missed.
 
   When not specified, \code{mult} takes its default depending on the \code{how} argument:
   \enumerate{
-    \item{ When \code{how \%in\% c("left", "inner", "full", "right")}, \code{mult="error"}. }
-    \item{ When \code{how \%in\% c("semi", "anti")}, \code{mult="last"}, although this is equivalent to \code{mult="first"}. }
-    \item{ When \code{how == "cross"}, \code{mult="all"}. }
+    \item When \code{how \%in\% c("left", "inner", "full", "right")}, \code{mult="error"}.
+    \item When \code{how \%in\% c("semi", "anti")}, \code{mult="last"}, although this is equivalent to \code{mult="first"}.
+    \item When \code{how == "cross"}, \code{mult="all"}.
   }
 
   When the \code{on} argument is missing, it will be determined based \code{how} argument:
   \enumerate{
-    \item{ When \code{how \%in\% c("left", right", "semi", "anti")}, \code{on} becomes the key column(s) of the \emph{join-to} table. }
-    \item{ When \code{how \%in\% c("inner", full")}, if only one table has a key, then this key is used; if both tables have keys, then \code{on = intersect(key(lhs), key(rhs))}, having its order aligned to shorter key. }
+    \item When \code{how \%in\% c("left", right", "semi", "anti")}, \code{on} becomes the key column(s) of the \emph{join-to} table.
+    \item When \code{how \%in\% c("inner", full")}, if only one table has a key, then this key is used; if both tables have keys, then \code{on = intersect(key(lhs), key(rhs))}, having its order aligned to shorter key.
   }
 
   When joining tables that are not directly linked to a single table, e.g. a snowflake schema (see References), a \emph{right} outer join can be used to optimize the sequence of merges, see Examples.

man/subset.data.table.Rd

@@ -9,7 +9,7 @@
 }
 
 \usage{
-  \method{subset}{data.table}(x, subset, select, \ldots)
+  \method{subset}{data.table}(x, subset, select, ...)
 }
 
 \arguments{

man/test.data.table.Rd

@@ -1,6 +1,6 @@
 \name{test.data.table}
 \alias{test.data.table}
-\title{ Runs a set of tests. }
+\title{ Runs a set of tests }
 \description{
   Runs a set of tests to check data.table is working correctly.
 }

man/transform.data.table.Rd

@@ -10,8 +10,8 @@
   \code{within}, \code{transform} and other similar functions in \code{data.table} are not just provided for users who expect them to work, but for non-data.table-aware packages to retain keys, for example. Hopefully the faster and more convenient \code{data.table} syntax will be used in time. See examples.
 }
 \usage{
-\method{transform}{data.table}(`_data`, \ldots)
-\method{within}{data.table}(data, expr, \ldots)
+\method{transform}{data.table}(`_data`, ...)
+\method{within}{data.table}(data, expr, ...)
 }
 \arguments{
   \item{data, _data}{ data.table to be transformed.}