more robust module object dependency checking #126
need to be able to identify dependency conflicts in modules:
Provide a function that the user can use to specify module object dependencies. Upon simulation initialization, temporarily store this info for each module in the spades environment, then concatenate into a single dataframe (or similar) that will be stored inside the
At a minimum, each module should present
If dependencies aren't met (i.e., there is a conflict in any of the above) produce an error. In the case of object name or class conflict, suggest using a "translator" module which may be available to convert data objects.
Object dependencies should be checked in the global environment AND the outputs of other modules that will be loaded in the simulation.
The text was updated successfully, but these errors were encountered:
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