Stream: IG creation
Topic: Custom template CI build confusion
David deRoode (Jul 23 2021 at 19:23):
Wondering why this custom template appears to fail in the CI build, yet it seems to still render using the HL7 Official template. Custom template repo is here: https://github.com/lantanagroup/ig-template-hl7-ada @Lloyd McKenzie
Lloyd McKenzie (Jul 23 2021 at 19:55):
@David deRoode Do you have a link to a build log showing the failure?
David deRoode (Jul 23 2021 at 20:01):
The CI build apparently built successfully, although the CI build dashboard (https://fhir.github.io/auto-ig-builder/builds.html) shows the most recent Dental build failed. Odd is all. Nevertheless, need to publish with custom template based on HL7 template; yet custom template in the HL7 Github site (https://github.com/HL7/dental-data-exchange/tree/master) is not being recognized, and is missing ADA.png somehow
Lloyd McKenzie (Jul 23 2021 at 20:14):
You can't have a custom template that has any scripts in it and use the CI-build.
Lloyd McKenzie (Jul 23 2021 at 20:14):
The only templates with scripts that the CI-build will run are ones that are hard-coded into the publisher as 'trusted' and which have a very tight group of committers. What were you trying to do with the scripts?
David deRoode (Jul 23 2021 at 20:24):
Nothing extra- nothing beyond continuing to trigger/enforce the standard HL7 validation. Simply trying to add the ADA logo in the header alongside the HL7 logo.
Jose Costa Teixeira (Jul 23 2021 at 20:26):
your custom templat e folder has a few xslts
Jose Costa Teixeira (Jul 23 2021 at 20:27):
with those, it won't run
David deRoode (Jul 23 2021 at 20:45):
Thanks! I removed scripts and now see the ADA logo in the CI build. But the FHIR and Search (magnifying glass) have unexpectedly disappeared. Also, I edited hl7.css to float the ADA logo to the right, but it's rendering on the left.
Lloyd McKenzie (Jul 23 2021 at 20:57):
Your custom template should only include the files that are different from the base. Anything that's the same as the base should be omited.
Lloyd McKenzie (Jul 23 2021 at 20:58):
In general, you shouldn't edit any css files. Instead, define your own CSS and add it to the list of those supported. That ensures that future changes to the base css will cascade through to your template.
David deRoode (Jul 26 2021 at 14:34):
Thanks @Lloyd McKenzie and @Jose Costa Teixeira. This clarifies how the templates reference/build. FYI @Rick Geimer
Last updated: Apr 12 2022 at 19:14 UTC
