cqframework / cqframework/cql-tests
Empty collection comparison
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 8
- Avg merge
- 12d 5h
- Merged PRs (30d)
- 2
Description
In FHIRPath, {} = {} is expected to evaluate to {} (an empty collection) as per the spec and FHIRPath tests.
The existing CQL test here contradicts the FHIRPath test and should be changed to expect an empty collection. null fits here well. This is already implemented in the Java engine.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tests/cql/CqlListOperatorsTest.xml at the referenced line and compare its empty-collection comparison expectation with the linked FHIRPath specification, test case, and Java engine test. Done means the CQL test expects an empty collection, represented by null, consistently with those references.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100