From 858f743d9a1319a1b05a1aaa36bc4d8c9382e694 Mon Sep 17 00:00:00 2001 From: John Grimes Date: Wed, 26 Jun 2024 10:43:05 +1000 Subject: [PATCH] Fix incorrect expectations on getReferenceKey without and right type specifier These should be false, as `link.other.getReferenceKey()` should return a key for `Patient/p3`. The absence of the type specifier should not cause this to return an empty collection, rather the collection should be unconstrained by the type of the reference. In the case where it is the right type specifier, it should also return a non-empty collection. --- tests/fn_reference_keys.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/fn_reference_keys.json b/tests/fn_reference_keys.json index ed03d35..157c2d4 100644 --- a/tests/fn_reference_keys.json +++ b/tests/fn_reference_keys.json @@ -48,7 +48,7 @@ "key_equal_ref": true }, { - "key_equal_ref": null + "key_equal_ref": false } ] }, @@ -73,7 +73,7 @@ "key_equal_ref": true }, { - "key_equal_ref": null + "key_equal_ref": false } ] },