After discussion, we would like to merge Eido back into Peppy as well as add some functionality to validation.
Currently, Eido primarily validates post-processed PEPS. However, it may be useful to do pre-processed validation. Our example PEP schema contains both sample and project level attributes but Eido is only validating Sample once they have been processed.
Therefore, during the merge of Eido into Peppy, we should also add a couple of functions:
pre-processd PEP validation -> eido takes the project level attributes and validates them against what is supplied in the pep_config
validate the original samples
Once the above have passed, eido can continue to validate the post-processed objects just as it current does.
After discussion, we would like to merge Eido back into Peppy as well as add some functionality to validation.
Currently, Eido primarily validates post-processed PEPS. However, it may be useful to do pre-processed validation. Our example PEP schema contains both sample and project level attributes but Eido is only validating Sample once they have been processed.
Therefore, during the merge of Eido into Peppy, we should also add a couple of functions:
Once the above have passed, eido can continue to validate the post-processed objects just as it current does.