Prevent logging an error when a parent that was fished using fishForFHIR does not have a mapping array. I don't think we should be logging this error regardless, so this PR adds a quick fix to prevent the error.
The error itself came up because a dependency that was used had an SD that was a profile's parent and did not have a mapping array on it, which is likely because SUSHI now only adds new or changed mappings, unless SUSHI uses --snapshot mode. I'm not sure if the fact that it has come up that at least one package is being published without mappings means we should consider other times to regenerate the full mapping list rather than just in --snapshot mode or relying on the IG Publisher to create it. I think this PR is relevant, regardless of what we decide about that, but we can decide whether another follow on task is needed.
Fixes #1454
Prevent logging an error when a parent that was fished using
fishForFHIRdoes not have amappingarray. I don't think we should be logging this error regardless, so this PR adds a quick fix to prevent the error.The error itself came up because a dependency that was used had an SD that was a profile's parent and did not have a
mappingarray on it, which is likely because SUSHI now only adds new or changed mappings, unless SUSHI uses--snapshotmode. I'm not sure if the fact that it has come up that at least one package is being published without mappings means we should consider other times to regenerate the fullmappinglist rather than just in--snapshotmode or relying on the IG Publisher to create it. I think this PR is relevant, regardless of what we decide about that, but we can decide whether another follow on task is needed.