Stream: conformance
Topic: Simplifier dependency to latest build / current
Patrick Werner (Aug 17 2020 at 10:16):
I am tried to add a dependency to the Genomics IG current build in Simplifier and failed. @Ward Weistra is there planned support for version=current? Would be quite important when developing derived IGs while the parent is still not 100% stable.
Ward Weistra (Aug 17 2020 at 13:46):
I understand that would be useful @Patrick Werner! Please help me think how that should work. The IG in question is the Genomics Reporting Implementation Guide on build.fhir.org? Currently only the package releases are ending up in the package registry.
I understand this is the behaviour of the IG publisher:
- If version is
dev: It looks in only in your local cache - If version is
current: It looks first in your local cache, if not current anymore or not available looks in https://build.fhir.org/ig/ - If version is anything else: It looks first in your local cache, if not available looks in packages.fhir.org (==packages.simplifier.net)
I think for Simplifier I'd like current to refer to the current state of a project (the project linked to that package name). Question is how Simplifier should figure out where it should look for the current version, especially when there is not yet a released version of package yet.
Or should the user know where the project is being developed and should we go to current-simplifier, current-fhirorg, etc. (there's more places where packages come from). :thinking:
Patrick Werner (Aug 17 2020 at 14:03):
Thanks for the fast reply.
Patrick Werner (Aug 17 2020 at 14:04):
I think the current source for packages is the hl7 package registry and simplifier. So current-simplifier and current-fhirorg could work.
Patrick Werner (Aug 17 2020 at 14:04):
current-fhirorgwould point to the latest build on https://build.fhir.org/ig/, current-simplifierto the current simplifier version of the project
Patrick Werner (Aug 17 2020 at 14:05):
Or, to enable interoperability, just go with current, and let the user decide the source of the package (hl7/simplifier)
Ward Weistra (Aug 17 2020 at 14:53):
Patrick Werner said:
Or, to enable interoperability, just go with current, and let the user decide the source of the package (hl7/simplifier)
I would prefer everyone being able to add current, but currently that would require another parameter per package to specify where it comes from, which wouldn't make it any different from current-fhirorg, etc. Unless we can infer from something else where a resolver should look.
Apparently, we have the basics in Simplifier ready for supporting relying on a current version of a Simplifier project, referenced to by the urlkey of the project. But that wouldn't work outside Simplifier, just like the IG Publisher implementation of current doesn't work with development projects outside of build.fhir.org...
Grahame Grieve (Aug 17 2020 at 19:21):
that can be fixed... For instance, the package registry could subscribe to build.fhir.org in real time (or close to it) and allow updating of current
Last updated: Apr 12 2022 at 19:14 UTC
