Open lmckenzi opened 2 years ago
Could this be an invariant in the IG that throws an error? We can embed this invariant/profile in the templates and let the validation logic do the work, instead of adding code.
It should be done by the template somehow - whether an invariant in an auto-applied profile, an XSLT check, or something else, I don't much care...
Agree this is on template. For portability and maintainability, I think a profile would be best
Tie this into the existing code that's already looking at the package-list file, etc. as part of Jira processing. Can check for CI-build, canonical and id all being HL7.
Enforce that the ig id and URL are based in HL7 and, if we can, enforce that the Git location is HL7 - so that we don't have issues with non-HL7 IGs using the HL7 template.