Stream: shorthand
Topic: SUSHI 1.0.0 Beta 2
Julia Afeltra (Oct 16 2020 at 17:19):
Announcing SUSHI 1.0.0 Beta 2 with the following enhancements and bug fixes:
- Supports setting the resource description in the generated ImplementationGuide on conformance and terminology resources only
- Avoids generating a duplicate resource when a resource is provided in input and defined in FSH
- Correctly extracts SUSHI configuration information from a provided ImplementationGuide resource
- Skips the processing of XML files that appear to be spreadsheets
- Fixes a bug where SUSHI specific comments were appended to input files
- Fixes a bug that allows uses the current working directory as the input directory if is not specified
- Resets the errors and warnings in between invocations of
fshToFhir
For more information, check out the Release Notes on GitHub.
Jose Costa Teixeira (Oct 19 2020 at 11:04):
I get this:
Sushi: warn The FSHOnly property is set to true, so no output specific to IG creation will be generated. The following properties are unused and only relevant for IG creation: parameters, copyrightYear, releaseLabel, template, menu.
Jose Costa Teixeira (Oct 19 2020 at 11:05):
Can this be an info?
Jose Costa Teixeira (Oct 19 2020 at 11:05):
I think if this is a warning, the CI build will never be clean
Chris Moesel (Oct 19 2020 at 13:20):
I'll talk to the team about this changing that log level from warning to info. That said, w/ FSHOnly projects using SUSHI 1.0.0, I'd recommend just letting SUSHI read in the IG JSON/XML file rather than using a sushi-config.yaml. I don't know your use case, but might it be better to take that approach here?
Jose Costa Teixeira (Oct 19 2020 at 13:38):
I didn't make a sushi.config.aml.
I think one is being created for me
Jose Costa Teixeira (Oct 19 2020 at 13:39):
could that be?
Chris Moesel (Oct 19 2020 at 13:57):
Oh... hmmm... do you have a package.json file? If so, then we might be generating a config from that. We used to use package.json for config, and when we switched to config.yaml, we put in logic that would transform the package.json to config.yaml to ease the transition. We may want to consider removing that code at this point. Is that maybe what is happening?
Jose Costa Teixeira (Oct 19 2020 at 15:12):
yes, I deleted te package.json file, I think that solved it (i will confirm when my IG is actually building again)
Jose Costa Teixeira (Oct 19 2020 at 15:12):
thanks
Last updated: Apr 12 2022 at 19:14 UTC
