Preserve FHIR types for Liquid loop variables - #92
Merged
Merged
Conversation
Keep internal FHIRPath resource nodes across template evaluations so unprefixed Liquid loop variables retain polymorphic property typing. Resolve nodes only at boolean and rendering boundaries, with regression coverage for Extension.value. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Exclude hidden tabs from the active split-pane set and avoid switching away from an output tab that is already visible after template evaluation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://thankful-water-06b155100-92.eastasia.4.azurestaticapps.net |
1 similar comment
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://thankful-water-06b155100-92.eastasia.4.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-plant-0209dde10-92.centralus.3.azurestaticapps.net |
1 similar comment
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-plant-0209dde10-92.centralus.3.azurestaticapps.net |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Liquid loop variables lost their FHIR type metadata between expression evaluations, so unprefixed access such as
i.valuecould not resolve polymorphic properties while%i.valuecould.This keeps FHIRPath
ResourceNodevalues intact across template evaluations and unwraps them only at boolean and rendering boundaries. As a result, prefixed and unprefixed loop-variable access now resolveExtension.valueconsistently without exposing internal node wrappers to custom renderers.Regression coverage verifies string and markdown Extension values, boolean evaluation, and resolved custom-renderer inputs.