Skip to content

Handle finding IG URLs for release-specific packages with incorrect packageIds#1614

Merged
jduteau merged 1 commit intomasterfrom
fix-ig-url-resolution
Mar 8, 2026
Merged

Handle finding IG URLs for release-specific packages with incorrect packageIds#1614
jduteau merged 1 commit intomasterfrom
fix-ig-url-resolution

Conversation

@cmoesel
Copy link
Copy Markdown
Member

@cmoesel cmoesel commented Mar 8, 2026

Description: Some release-specific packages (e.g., hl7.fhir.eu.extensions.r4) don't include the correct packageId in their ImplementationGuide resource; they might have a packageId like hl7.fhir.eu.extensions.4.0.1. Update the IG Exporter to handle this case so it can still find the correct IG URL for affected release-specific package dependencies.

Testing Instructions: Unit tests demonstrate the fix. You can also try setting up a simple SUSHI project with hl7.fhir.eu.extensions.r4 as a dependency. The currently released SUSHI will export an IG with the dependency's URL as http://hl7.eu/fhir/extensions. This PR branch will export an IG with the dependency's URL as http://hl7.eu/fhir/extensions/ImplementationGuide/hl7.fhir.eu.extensions (which is correct).

Related Issue: https://chat.fhir.org/#narrow/channel/215610-shorthand/topic/ImplementationGuide.20URL.20missing/near/576162330

@cmoesel cmoesel requested a review from jduteau March 8, 2026 01:51
Copy link
Copy Markdown
Collaborator

@jduteau jduteau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me and I tested it out

@jduteau jduteau merged commit 828b025 into master Mar 8, 2026
14 checks passed
@cmoesel cmoesel deleted the fix-ig-url-resolution branch March 8, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants