Set ValueSetRef.preserve to true for included value sets #1409
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.
Closes #1407.
Starting with version 1.5,
ValueSetRef
s need to havepreserve
set to true during translation so that ValueSetRefEvaluator does not expand them during execution. Currently, this is only applied to theValueSetRef
s that point to value sets from the same library and not when the value set comes from an included library (i.e. not whenValueSetRef
s are constructed from importedValueSetDef
s). The fix is to setValueSetRef.preserve
to true in both cases.