Create documentation paradigm for modules #125
Module metadata at top of the module's
Hosted in a separate GitHub repo (
Module data will NOT be included/hosted in our repo. They must be accessible elsewhere, and code/instructions for this step should be included in the module documentation.
Modules can be contributed to our repo via pull requests, which also provides easier quality assurance on our part with respect to contributed modules' structure and documentation.
Module directory structure:
part of #125 and #126 - use two separate files for module metadata & code - `metadata.R` sourced to local env. - `moduleName.R` code sourced to `.GlobalEnv` - update module template and sample modules to reflect this - remove function `prevArgs` and reintegrate code in `.objectNames` - separate dependency classes and methods into two R files