If source JSON uses cross-version extensions, GoFSH recognizes it enough to emit an error saying to add the extension to your dependencies, but does not add it for you. As a result, when a profile specifies a cross-version extension, GoFSH incorrectly translates it as an inline extension instead of a standalone extension.
Unfortunately, specifying the cross-version dependency on the commandline (e.g., -d hl7.fhir.extensions.r5@4.0.1) also does not work, as GoFSH apparently doesn't know how to load that virtual package (because it's actually quite complicated).
Probably the best way to handle this is to detect cross-version extensions in an optimizer and convert them to standalone extensions in profiles even if it doesn't know the definition. And it should add the relevant cross-version dependency to the config.
If source JSON uses cross-version extensions, GoFSH recognizes it enough to emit an error saying to add the extension to your dependencies, but does not add it for you. As a result, when a profile specifies a cross-version extension, GoFSH incorrectly translates it as an inline extension instead of a standalone extension.
Unfortunately, specifying the cross-version dependency on the commandline (e.g.,
-d hl7.fhir.extensions.r5@4.0.1) also does not work, as GoFSH apparently doesn't know how to load that virtual package (because it's actually quite complicated).Probably the best way to handle this is to detect cross-version extensions in an optimizer and convert them to standalone extensions in profiles even if it doesn't know the definition. And it should add the relevant cross-version dependency to the config.