-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove old CVR code from VxAdmin (#3999)
* Remove old-format CVR fixture data * Indicate which files in libs/fixtures are generated So that the GitHub UI collapses them by default * Generate new-format CVR fixture data using libs/cvr-fixture-generator From libs/cvr-fixture-generator: $ ./bin/generate \ -p ../fixtures/data/electionGridLayoutNewHampshireAmherst/election.json \ -o ../fixtures/data/electionGridLayoutNewHampshireAmherst/castVoteRecords/generated $ ./bin/generate \ -p ../fixtures/data/electionTwoPartyPrimary/election.json \ -o ../fixtures/data/electionTwoPartyPrimary/castVoteRecords/generated * Add manually prepared new-format CVR fixture data * Update build_resources.sh in libs/fixtures * Run `pnpm build:resources` in libs/fixtures * Update relevant fixtures' index.ts files * Delete legacy_import.test.ts Since it relies on old CVR fixtures and legacy_import.ts will itself soon be deleted * Update libs/utils tests * Add a modifyCastVoteRecordExport fxn for modifying fixtures for tests Also use more consistent variable names for raw file contents vs. parsed contents * Move helper for listing CVR exports out of legacy_cast_vote_records.ts And then delete legacy_cast_vote_records.ts * Remove old code paths from VxAdmin backend app.ts * Update VxAdmin frontend to account for backend updates * Update VxAdmin backend tests * Set up getExportedCastVoteRecordIds helper * Use constants for file names * Use alternative import syntax to fix frontend builds * Use build-stubs script to build fs stub in frontends missing that stub * Distinguish no-entity from not-directory
- Loading branch information
1 parent
3ba81d4
commit 1483679
Showing
719 changed files
with
286,470 additions
and
161,372 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.