Closed lukey-luke closed 3 months ago
116 tests ±0 116 :white_check_mark: ±0 37s :stopwatch: +3s 34 suites ±0 0 :zzz: ±0 34 files ±0 0 :x: ±0
Results for commit 4f2f54de. ± Comparison against base commit aa3e3006.
:recycle: This comment has been updated with latest results.
Overall Project | 67.02% | :x: |
---|
There is no coverage information present for the Files changed
Should we update the name for the autosuggestion csv file as well? In the data folder it is named with the PACT act release, but in the new master spreadsheet it is named as "Suggested Conditions v[ ]". This also matches Eva's comment in the zenhub ticket regarding file names.
Should we update the name for the autosuggestion csv file as well? In the data folder it is named with the PACT act release, but in the new master spreadsheet it is named as "Suggested Conditions v[ ]". This also matches Eva's comment in the zenhub ticket regarding file names.
@tyler-spangler6 I don't recall this from the synchronous conversation we had prior, but I found [Release notes] Auto-suggestions release notes on google drive and added the Suggested Conditions v1.1 Flat
tab to abd-vro
What was the problem?
"classification_code"
and"classification_name"
in order to get access to both pieces of information at the same timeAssociated tickets or Slack threads:
How does this fix it?[^1]
How to test this PR
/classifier
and/vagov-claim-classifier
pytest
[^1]: Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. [^secrel]: To check if a PR will succeed in the SecRel workflow, test PRs in the SecRel pipeline.