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

Thrown out tossup/bonus needs rework #212

Open
alopezlago opened this issue May 13, 2023 · 1 comment
Open

Thrown out tossup/bonus needs rework #212

alopezlago opened this issue May 13, 2023 · 1 comment
Labels
enhancement New feature or request High priority High priority issues

Comments

@alopezlago
Copy link
Owner

MODAQ was designed for handling thrown out tossups in the old way, which was that a replacement question would be read at the end. Most tournaments now have a packet of replacement questions, which means that throwing out a question should instead prompt for a replacement question, and then that question is tracked separately.

This needs a lot of design work.

@alopezlago alopezlago added the enhancement New feature or request label May 13, 2023
@alopezlago alopezlago added the High priority High priority issues label Jul 2, 2023
@alopezlago
Copy link
Owner Author

So the flow should look something like this:

  • User clicks on the X or the menu button to throw out a question
  • A dialog appears asking the user how they would like to replace the question:
    • Go to the next available question
    • Insert a replacement question
      • There is a button for loading the packet, and a spinner for which question to pick from the packet

One challenge here is handling the case where one team negs on a question, and then a replacement is read. You have to keep both questions around, but MODAQ currently assumes that there is one tossup per question. We have to change the internal state to indicate when a question is just a replacement, which will make the logic more complicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request High priority High priority issues
Projects
None yet
Development

No branches or pull requests

1 participant