Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/milestone3 #113

Merged
merged 17 commits into from
Apr 18, 2024
Merged

Feature/milestone3 #113

merged 17 commits into from
Apr 18, 2024

Conversation

windoverwater
Copy link
Collaborator

Not completely working but milestone 3 is close enough. Ended up with several design significant refactoring changes:

  • changed the low-level ballot format (and config.yaml format) such that the contests node of the ballot data model is an array instead of a dictionary.
  • the ElectionConfig is now a real singleton pattern - it is only every created once per election
  • created a real webapi class to hold functions for that
  • the ballot receipt is now stored as a bare csv file and not a markdown
  • the QR svg is now being passed back to the client side (incorrectly but at least passed back)
  • the Operation class is no longer a singleton

This was done to support milestone3 features in the client side

@windoverwater windoverwater self-assigned this Apr 18, 2024
@windoverwater windoverwater merged commit ffe4151 into main Apr 18, 2024
2 checks passed
@windoverwater windoverwater deleted the feature/milestone3 branch April 18, 2024 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant