Closed jag3773 closed 3 years ago
The textTranslation_derived metadata from the doc examples artifacts has ingredients like release/text/USX_1/OTINT.usx
. Are those files something I could include in the test repo or should I completely fabricate new ingredients for this test repo?
Also, I can easily verify by hash but how much other validation should I do of ingredient file format?
Regarding
Also, I can easily verify by hash but how much other validation should I do of ingredient file format?
I notice that existing test repos don't have any automated testing even of hashing. Is that something we want to add to a validation suite?
Yes, the current spec is very minimal on ingredient specification and/or validation. In general, we want to be more particular about ingredients (you know, Non-GMO, Organic, Gluten-Free, etc.).
removed the recipe spec requirement
You can use a subset of https://github.com/bible-technology/sb_textTranslation/tree/master/ingredients .
Gospel subset moved over, realistic updates to metadata and size/checksums now work out.
Definition of Done
metadata.json