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

Add corner case where the description from a data type profile used in a derived profile isn't used #201

Conversation

pieter-edelman-nictiz
Copy link
Contributor

No description provided.

@grahamegrieve
Copy link
Collaborator

@pieter-edelman-nictiz
Copy link
Contributor Author

It's a bit different (and admittedly, a bit involved).

  • First, there's a 'zib' layer with a profile that uses a data type profile. My expectation here would be that the profile renders the description from the data type profile (which is indeed the case).
  • Then there's an 'nl-core' layer, where the original profile is derived. In this derived profile, the original use of the data type profile is overwritten by the use of another data type profile, with another description. My expectation is that the derived profile renders the description from the overwriting data type profile instead of the original data type profile. This is currently not the case for the Validator.

@grahamegrieve grahamegrieve merged commit d74860b into FHIR:master Nov 25, 2024
2 of 5 checks passed
@grahamegrieve
Copy link
Collaborator

So I expected that after I merged this, the test would fail until I fixed the actual snapshot code, but no?

@pieter-edelman-nictiz
Copy link
Contributor Author

So I expected that after I merged this, the test would fail until I fixed the actual snapshot code, but no?

It doesn't fail? That's weird. If I create a snapshot using the latest version of the Validator (6.4.4), the comment on CarePlan.contributor:requester in the snapshot is the comment from the 'zib' data type profile. I've manually adjusted this in "nl-core-NursingIntervention-output.json" to the comment from the 'nl-core' data type profile as the desired behavior.

@grahamegrieve
Copy link
Collaborator

well, where's the specific bit in the expected outcome that you changed?

@pieter-edelman-nictiz
Copy link
Contributor Author

In two places, see these screenshots. On the left is the output as produced by the Validator, on the right is the output in this PR.

nl-core-diff2

nl-core-diff1

@pieter-edelman-nictiz
Copy link
Contributor Author

Note: conversion was done using -version 4.0.1

@grahamegrieve
Copy link
Collaborator

can you look at this: #203

which of these changes are pertinent to the test case?

@pieter-edelman-nictiz
Copy link
Contributor Author

I added pull request comments

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