Stream: committers
Topic: IG dependencies
Grahame Grieve (Nov 11 2019 at 02:08):
I've just discovered a significant problem with the build process. The build process requires that you specify your dependencies in the ig.json file, but doesn't require that the same dependencies are found in the IG resource itself.
And the package.tgz dependencies are populated from the IG resource, not the ig.json.
I have 3 choices to ix this:
- require that the IG dependencies match the ig.json ones, or else halt the publication run
- require that the IG dependencies match the ig.json ones, or else put an error in qa.html
- populate the IG dependencies automatically
Of these, I strongly prefer #3, and I'm going to implement it now, as a workaround, but if people want to argue for one of the others, here's your opportunit.y
Richard Townley-O'Neill (Nov 11 2019 at 03:28):
@Grahame Grieve
Does option 3 mean that there is no need to include dependencies in the ig.json as what is in the implementation guide will drive all dependencies?
Grahame Grieve (Nov 11 2019 at 03:31):
no the other way around
Richard Townley-O'Neill (Nov 11 2019 at 04:08):
The the publisher will create an implementation guide with exactly the the dependencies found in the ig.json, and will ignore any dependency information in the source implementation guide.
Richard Townley-O'Neill (Nov 11 2019 at 04:09):
Just as happens with the FHIR version: the FHIR version in the ig.json becomes the FHIR version in the generated implementation guide.
Grahame Grieve (Nov 11 2019 at 04:22):
The publisher will create an implementation guide with exactly the the dependencies found in the ig.json, and will ignore any dependency information in the source implementation guide
No. It will ensure that whatever is in ig.json is in the IG resource, but it will not delete anything from the IG
John Moehrke (Nov 11 2019 at 16:26):
The less we can look to the ig.json the better... so I would prefer the IG resource is used. If this isn't possible, then errors need to be thrown and the publisher should be stopped.
Grahame Grieve (Nov 11 2019 at 19:24):
it's transient anyway - we are moving to not use ig.json
Last updated: Apr 12 2022 at 19:14 UTC
