Repository navigation
Add a FHIRPath case that checks a dateTime comparison doesn't change the compared value - #319
Merged
Merged
Conversation
…the compared value
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
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.
testLessThan28 (r4, r4b, r5, r6) compares the patient birthTime extension, 1974-12-25T14:35:45-05:00, with @1975-01-01T00:00:00Z and then checks that the value still reads 1974-12-25T14:35:45-05:00. The Java engines convert both operands to UTC in place, so by then the value is 1974-12-25T19:35:45Z and the case fails in all four. The fix is hapifhir/org.hl7.fhir.core#2776.