Adds full functionality for the Next Match button. Since the match list changes during the event and there's no clear "correct" ordering, we instead rely on parsing match keys to guess the next match and accept the guess if it's in the match list, refreshing the match list once if necessary.
The full algorithm is:
Client sends a request to the server to return possible next matches (this is because the server has better abstractions around parsing match keys that aren't worth replicating to the frontend)
Server responds with up to 2 matches:
The next match in the same tournament phase (ex: qual 1 -> qual 2)
The first match in the next tournament phase (ex: qual 34 -> playoff 1)
Client checks its current match list to see if option 1 is in the match list, or if not, if option 2 is in the match list
If neither match suggestion exists, refresh the match list and try again
If neither match suggestion exists still, show an error
Due to low usage of best of 3 playoffs nowadays, this feature only supports double eliminations. A warning appears if the Next Match button can't be used because of the current playoffs type.
Adds full functionality for the Next Match button. Since the match list changes during the event and there's no clear "correct" ordering, we instead rely on parsing match keys to guess the next match and accept the guess if it's in the match list, refreshing the match list once if necessary.
The full algorithm is:
Due to low usage of best of 3 playoffs nowadays, this feature only supports double eliminations. A warning appears if the Next Match button can't be used because of the current playoffs type.
Closes #62