Closed elsaperelli closed 1 year ago
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π’ | Statements | 85.39% (-0.03% π») |
2023/2369 |
π‘ | Branches | 73.97% (-0.02% π») |
1802/2436 |
π’ | Functions | 87.5% | 357/408 |
π’ | Lines | 85.69% (-0.04% π») |
1952/2278 |
379 tests passing in 29 suites.
Report generated by π§ͺjest coverage report action from a05e87921cdd99ffd594ad9de6d3cd750c39c717
While we're here, can we finally just comment out this unused variable (don't remove it) so that lint passes without warnings? https://github.com/projecttacoma/fqm-execution/pull/219/files#file-src-calculation-clauseresultsbuilder-ts-L354
While we're here, can we finally just comment out this unused variable (don't remove it) so that lint passes without warnings? https://github.com/projecttacoma/fqm-execution/pull/219/files#file-src-calculation-clauseresultsbuilder-ts-L354
Yes, OIDs were used in QDM land to reference codesystems. But now we use sane canonical URLs in FHIR. Definitely can be removed.
Summary
This PR upgrades the typescript version to the latest version, 5.0.4.
New behavior
Code changes
jest
andts-jest
versions as well. If for whatever reason we want to maintain the old jest version, then I would have to downgrade the typescript version to4.9.5
.typescript-eslint
dependencies.ts-jest
in globals was deprecated, so I changedjest.config.js
to reflect the currentts-jest
installation docs.Error handling changes:
ValueSetResolver.ts
- This approach is consistent to what we do inExecution.ts
. The alternative is to do:catch (e: any)
orcatch (e: unknown)
.MeasureBundleHelpers.test.ts
/parseQueryInfo.test.ts
- I thought this was a better approach thancatch (e: any)
, but let me know if that doesn't make sense.Testing guidance
npm run check
Make sure there are no new warnings or errors and that all tests pass.