Batch audit file prep tool: Handle extra spaces in Dominion CVR contest headers #2053
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.
Overview
We've been seeing some Dominion files from Georgia with an extra space between contest names and the number of votes allowed in contest headers, e.g.,
Contest 1 (Vote For=1)
as opposed toContest 1 (Vote For=1)
.This is not true for all files across the state and likely has to do with different people managing programming for different jurisdictions, so we can't just add an extra space to the contest name in the Arlo audit config.
While we're advising jurisdictions on how to correct, this may be widespread enough that it's worth us just handling this automatically. That's what this PR does - it trims the extra spaces down to a single space.
Testing