Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support FHIR-release-specific "current" build dependencies #43

Open
cmoesel opened this issue Dec 5, 2024 · 0 comments
Open

Support FHIR-release-specific "current" build dependencies #43

cmoesel opened this issue Dec 5, 2024 · 0 comments

Comments

@cmoesel
Copy link
Member

cmoesel commented Dec 5, 2024

The package loader currently cannot find some FHIR-release-specific dependencies (for example, hl7.fhir.uv.extensions.r4#current). This is because that package is not explicitly listed in the qas.json file.

Add support for this by using the following approach:

  1. Look for the dependency as-is (e.g., hl7.fhir.uv.extensions.r4); if found, use it; otherwise...
  2. If the package id ends with an r number (e.g., matches /\.r\d+$/), remove the end and search for the base package (e.g., hl7.fhir.uv.extensions); if found...
  3. Determine the package build folder on the build server per the normal approach and try to download a tgz w/ the name of the originally requested package (e.g., https://build.fhir.org/ig/HL7/fhir-extensions/branches/master/hl7.fhir.uv.extensions.r4.tgz). If found, use it; otherwise...
  4. Download the base package (without the r[1-9] ending) as normal, but log a warning.

(I'm not sure about step 4, but it's worth considering. We could also check the package metadata to confirm if it is for the right FHIR release an only download it if it is. Or we could just give up).

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

No branches or pull requests

1 participant