You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 97be33d
Browse filesBrowse the repository at this point in the historyBrowse files
test: assert the repeating reference check instead of documenting its absence
Both example tests existed partly to record that the check never ran, and
forced it to execute with an invalid single-value cardinality to show what it
would do. They now exercise the list path directly.
`USCoreProvenance: field 'target' references '${reference.split("/")[0]}' but only Bundle, CodeSystem, Observation, OperationOutcome, Patient, Provenance are allowed`,
58
+
]);
68
59
});
69
60
70
-
test("the check rejects a type that is not a resource once it executes",()=>{
"USCoreProvenance: field 'target' references 'NotAResource' but only Bundle, CodeSystem, Observation, OperationOutcome, Patient, Provenance are allowed",
73
69
]);
74
70
});
71
+
72
+
// One error per offending type, so a list of many wrong references of the
73
+
// same type does not bury the rest of validate()'s output.
74
+
test("a repeated offending type is reported once",()=>{
0 commit comments