Given that this package doesn't have any dependencies on other RMI-PACTA repos (either as "hard" Imports, or "soft" Suggests), running R CMD CHECK with the dev versions of r2dii.match and .analysis doesn't make much sense, since there isn't anything called from those repos.
Can anyone think of a reason to keep this check in here? @RMI-PACTA/r-developers
Given that this package doesn't have any dependencies on other RMI-PACTA repos (either as "hard"
Imports
, or "soft"Suggests
), running R CMD CHECK with the dev versions ofr2dii.match
and.analysis
doesn't make much sense, since there isn't anything called from those repos.Can anyone think of a reason to keep this check in here? @RMI-PACTA/r-developers
Context: I'm planning to ensure checks against dev-versions of dependencies in
.match
(https://github.com/RMI-PACTA/r2dii.match/pull/480).analysis
(https://github.com/RMI-PACTA/r2dii.analysis/issues/501) and.plot
(https://github.com/RMI-PACTA/r2dii.plot/issues/567) which captures the "upstream" direction, but do we need to capture "downstream" for some reason (if we're not executing any of that code)Relates to #386