Stream: IG creation
Topic: References to build.fhir.org
Grahame Grieve (Jun 22 2019 at 19:40):
The Davinci guides that we just published were full of hard coded references to build.fhir.org. I don't think we fixed them all. It's illegal to reference build.fhir.org in a published IG since it has no stable content. Yet authors keep doing it - why?
I haven't figured out what I can do in the tooling to stop this from happening.
Grahame Grieve (Jun 22 2019 at 19:42):
some technical background: as long as your dependency version is current you are referencing the current build. When you submit your guide for publishing, you cannot be referencing the current version, you have to reference a specific version.
Grahame Grieve (Jun 22 2019 at 19:42):
that's problematic for submitting a set of guides where one references another. I don't know what to do about that
Grahame Grieve (Jun 22 2019 at 19:44):
since this implies that the references will change, there's a way to reference a spec without hardcoding the path. - a jekyll variable {{ xx }} that you use instead of hardcoding the path to an IG. the IG Publisher will process the path to a right reference
Grahame Grieve (Jun 22 2019 at 19:45):
but because it's processed by jekyll, I don't know whether the output reference to build.fhir.org was hardcoded or a variable - so I can't check.
Grahame Grieve (Jun 22 2019 at 19:49):
the variable is site.data.fhir.[code] where code is the value you assigned to the ig in the ig.json file
Grahame Grieve (Jun 22 2019 at 19:50):
there are situations where it is valid to reference build.fhir.org.. namely: 'see xx for the current build' which is seen occasionally in IGs
Last updated: Apr 12 2022 at 19:14 UTC
