Can now use a discriminator to walk into a complex extension (for R3) #1671
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uld not find the complex child extension. Created a (valid) example of a profile that constrains a complex extension inline and fixed the walker to look for fixUri instead of a targetProfile.profile.
ewoutkramer
changed the title
marcovisserFurore
changed the title
marcovisserFurore
suggested changes
Mar 30, 2021
src/Hl7.Fhir.Specification.Tests/Hl7.Fhir.Specification.Tests.csproj
Outdated
Show resolved
Hide resolved
src/Hl7.Fhir.Specification/Specification/Navigation/StructureDefinitionWalker.cs
Show resolved
Hide resolved
marcovisserFurore
approved these changes
Mar 30, 2021
marcovisserFurore
deleted the
feature/1656-discriminating-complex-extensions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed a bug where a discriminator walking into a complex extension would not find the complex child extension.
Created a (valid) example of a profile that constrains a complex extension inline and fixed the walker to look for fixUri instead of a targetProfile.profile.
Related issues
Fixes #1656.
FirelyTeam Checklist