FHIR Chat · nested folders in /input/resources/abc · shorthand

Stream: shorthand

Topic: nested folders in /input/resources/abc


view this post on Zulip Martin Höcker (Mar 06 2022 at 23:26):

My project (minimum example here) contains resources in a subfolder input/resources/nested. If I understand the documentation of the newest sushi release v.2.3.0 correctly, I should be able to silence possible warning by adding the following snippet to sushi-config.yaml:

parameters:
  path-resource:
    - input/resources/nested

However, the warning about unsupported folders still comes up:

The following files were not added to the ImplementationGuide JSON because they are not in one of the supported input folders or are nested too deep in one of those folders. While SUSHI automatically supports resources in sub-folders, the IG Publisher does not, unless the folder is explicitly added via the template or an IG parameter. To fix any issues you may encounter due to this, adjust your IG parameters or template accordingly or move these files so they are directly under a supported input folder (e.g., input/resources, input/profiles, etc.):
  - /Users/I501618/SAPDevelop/health/TESTS/mwe/input/resources/nested/StructureDefinition-MyPatient.json

Are "nested" folders in input/resources officially not supported and/or recommended?

Related question (more of a nitpick, really...): Reading the related documentation about the IG Publisher Parameters, it seems that if the user specifies a path-resource-parameter, then the default location (input/resources) is ignored by the IG Publisher (this is my interpretation of the docs -- I have not tried this yet!). In contrast to this, sushi seems to interpret user-specified path-resource-parameters as _additional_ folders. Is this the intended behavior or am I misunderstanding something?

view this post on Zulip Chris Moesel (Mar 07 2022 at 14:56):

Hi @Martin Höcker. These are excellent questions.

  1. I think that the behavior with intput/resources/nested is unintentional. I think that is a use case that probably should work but we missed it. We'll have to take a look at that.

  2. Regarding whether path-resources defines additional paths or replaces the default paths... I think we assumed it is additional paths based on some prior conversations. I wouldn't trust the doc too much, as it says the default is "\resources", but our experience is that it is \input\resources, and also includes a number of other folders like \input\profiles, \input\extensions, \input\vocabulary, etc. That said, there is some interplay between the templates and the publisher, so that may be what we're seeing here. Anyway, we'll double-check our assumption and let you know what we find.

view this post on Zulip Chris Moesel (Mar 07 2022 at 17:32):

SUSHI-1037 and SUSHI-1038


Last updated: Apr 12 2022 at 19:14 UTC