Conversation
castelao
added
enhancement
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #427 +/- ##
==========================================
- Coverage 55.74% 55.68% -0.06%
==========================================
Files 62 62
Lines 5983 5985 +2
Branches 568 568
==========================================
- Hits 3335 3333 -2
- Misses 2589 2592 +3
- Partials 59 60 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Improves operator visibility during compass process runs by including the jurisdiction’s code (typically FIPS) alongside the human-readable jurisdiction name in the startup log message, helping catch mismatches/typos when local-file processing relies on FIPS-based matching.
Changes:
- Expanded the “Kicking off processing…” log line to include
jurisdiction.codein addition tojurisdiction.full_name.
|
Nice, more logging is always welcome (I guess within reason :P) |
Although we provide a list (CSV) of jurisdictions, when running with local files, the matching is done with FIPS. This will help to identify typos and other silly errors.
|
This is small enough that I will just merge. Thanks for this @castelao! |
* log: Informing FIPS with jurisdiction name Although we provide a list (CSV) of jurisdictions, when running with local files, the matching is done with FIPS. This will help to identify typos and other silly errors. * log: Trace level of FIPS for local documents * style: Breaking a long line
Although we provide a list (CSV) of jurisdictions, when running with local files, the matching is done with FIPS. This will help to identify typos and other silly errors.