Technically, logical model instances are not required to have a resourceType or id, but if you include a JSON instance of a logical model in any of the input/* resource folders, SUSHI will try to load it and will emit an error when it can't find resourceType/id.
@lmckenzi has suggested an approach to detect which of these files can be safely ignored by looking at the resource listing in sushi-config.yaml. We should investigate further and implement as suggested and/or only warn when resourceType can't be found (instead of error) since warnings can be suppressed.
Technically, logical model instances are not required to have a
resourceTypeorid, but if you include a JSON instance of a logical model in any of theinput/*resource folders, SUSHI will try to load it and will emit an error when it can't findresourceType/id.@lmckenzi has suggested an approach to detect which of these files can be safely ignored by looking at the resource listing in
sushi-config.yaml. We should investigate further and implement as suggested and/or only warn whenresourceTypecan't be found (instead of error) since warnings can be suppressed.See: https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/How.20do.20I.20get.20SUSHI.20to.20ignore.20a.20binary.20JSON.20logical.20instance.3F/near/407798801