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
fix bug in logic for exhaustIfMultipleContinuing overvote rule #610
Conversation
@@ -796,9 +796,9 @@ private OvervoteDecision getOvervoteDecision(Set<String> candidateSet) { | |||
if (continuingCandidate != null) { // at least two continuing | |||
decision = OvervoteDecision.EXHAUST; | |||
break; | |||
} else { | |||
continuingCandidate = candidate; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed.
OK, test added. |
same ask here... get rid of the test_set prefix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same ask here: remove the 'test_set' prefix from test files and names
Will do. Please accept the PRs preemptively so I can merge them as soon as I make these trivial updates (which might be at a weird time late tonight). |
This is a fun one. It definitely calls for a new test. Just waiting for guidance on the best way to do that.
Fixes #554.