Stream: IG creation
Topic: Setting "url" in package.json
Brian Kaney (Nov 02 2020 at 23:09):
When building an IG locally, how does one specify the "url" property in package.json (in the generated FHIR Package, package.tgz)?
Lloyd McKenzie (Nov 03 2020 at 01:39):
It should come from the ImplementationGuide.url value
Nick Freiter (Nov 03 2020 at 13:38):
When building a package locally, the url in package.json is getting set to a file path for me, so something like:
"url": "file://C:\Users\nfreiter\dev\ExampleIG\output"
I've confirmed the ImplementationGuide.url value is set to a url, not that filepath, and I'm still seeing the filepath. Do you know why that would be?
Grahame Grieve (Nov 03 2020 at 20:28):
what are you trying to achieve?
Brian Kaney (Nov 04 2020 at 01:20):
I would like to know how to specify the url property of package.json (that ends up in package.tgz). Presently it's generating a value like file:///path/to/ig.
Grahame Grieve (Nov 04 2020 at 02:47):
yes but why do you want to specify it?
Brian Kaney (Nov 04 2020 at 14:53):
So if someone in the organization that uses the FHIR Package would like to see "where the human readable representation (e.g. IG) that represents this version of this package is published on the web (if there is such a thing)", it could be specified (during our IG publishing CI/CD pipeline).
Grahame Grieve (Nov 04 2020 at 20:00):
well, you can set the value from the command line - the parameter -web [x] where [x] is the URL. The actual value will depend on your publishing policy and infrastructure.
Nick Freiter (Nov 04 2020 at 20:35):
This originally came up with an IG that was being created using SUSHI and the IG Publisher. Is setting that parameter from the command line the only way to do it? Just wondering if there would be some way for SUSHI to set a value in the content that it generates.
Grahame Grieve (Nov 04 2020 at 20:37):
there isn't at the moment. typically, you don't know necessarily know exactly where it's going to be published when authoring the guide
Nick Freiter (Nov 04 2020 at 20:43):
Right, that makes sense. I was a little confused in reading some of the package spec doc though. Came across this section which made me think manifest.rendering in the ImplementationGuide resource would be used to populate this url value. But I wasn't able to get that to work. Was I misreading something there? Or is the usage of manifest.rendering more dependent on the context?
Last updated: Apr 12 2022 at 19:14 UTC
