Running the Jest suite (npm test) surfaces nine pre-existing failures in the compliance suite (tests/compliance.test.js), unrelated to any current feature work. Recording them here so they are tracked separately.
fn_boundary.json - 8 failures. All boundary-function cases fail with Error: Not implemented: lowBoundary / highBoundary:
- decimal lowBoundary / highBoundary
- datetime lowBoundary / highBoundary
- date lowBoundary / highBoundary
- time lowBoundary / highBoundary
The bundled fhirpath dependency (4.10.1) does not implement the lowBoundary() / highBoundary() functions, so these cases cannot pass until the dependency provides them (or they are shimmed).
validate.json - 1 failure. where with path resolving to not boolean: the case sets expectError: true, but evaluation returns an empty result (actual: []) instead of raising an error. A where() whose path resolves to a non-boolean should be reported as an error rather than silently yielding no rows.
Running the Jest suite (
npm test) surfaces nine pre-existing failures in the compliance suite (tests/compliance.test.js), unrelated to any current feature work. Recording them here so they are tracked separately.fn_boundary.json- 8 failures. All boundary-function cases fail withError: Not implemented: lowBoundary/highBoundary:The bundled
fhirpathdependency (4.10.1) does not implement thelowBoundary()/highBoundary()functions, so these cases cannot pass until the dependency provides them (or they are shimmed).validate.json- 1 failure.where with path resolving to not boolean: the case setsexpectError: true, but evaluation returns an empty result (actual: []) instead of raising an error. Awhere()whose path resolves to a non-boolean should be reported as an error rather than silently yielding no rows.