fqm-execution bump to 1.3.1 and update Docker setup #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
1.3.1
). See here for the release notes.New behavior
npm run check
no longer results in those two lint errors fromecqm-content-r4-2021/input/images/cql.js
. I added a.eslintignore
file for theecqm-content-r4-2021
directory. I hope this is okay, let me know if it's not. I was tired of seeing those and now the prettier check seems to actually happen.upload-bundles
npm script now is able to handle a directory of nested MADiE Measures and TestCase export bundles.Note: these will not execute in the server at the moment due to issues with relatedArtifact references in the Measure and Library resources and patient data queries
Code changes
.eslintignore
- added this file to avoid those errors that we (I think) don't care aboutpackage.json
/package-lock.json
- further upgraded the fqm-execution versionexecQueue.js
- Updated to use newer MeasureReportBuilder API.Code changes Lauren made in previous fqm-e version bump PR
ci.yml
,measure.service.js
,base.service.test.js
Testing guidance
npm run check
Reminder that sometimes a couple of these tests will fail. That is okay for now and something we need to address in separate tasking.npm start
make sure that all functionality works the same.NOTE: