Decide how to handle sub-models in yaml |
||
Issue descriptionThe current schema supports sub-models, where most things can be overridden at that level. With yaml this is not implemented. Some models in Coral use sub-models, so this may need to be addressed. Alternatively, perhaps the concept of a 'project' would obviate this need, and people would then happily use separate models for each sub-model.
,
Mar 14 2018
yaml already solves this because submodels will just be blown out
,
Mar 14 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by jbudorick@chromium.org
, Mar 12 2018