The current way to generate draws is through making a POST request to /draws withe the event id as the body, and then calling /draws/confirm/:eventId. The problem with this approach, as noted in issue #3 is that the current algorithm is too slow and does not generate all possible combinations.
Instead, I propose that these draws be generated on the client side and sent to /draws/confirm/:eventId with a POST request with the body holding all draws. This will make for faster draw generation and also allow organizers to manually create pairings.
The current way to generate draws is through making a
POSTrequest to/drawswithe the event id as the body, and then calling/draws/confirm/:eventId. The problem with this approach, as noted in issue #3 is that the current algorithm is too slow and does not generate all possible combinations.Instead, I propose that these draws be generated on the client side and sent to
/draws/confirm/:eventIdwith aPOSTrequest with the body holding all draws. This will make for faster draw generation and also allow organizers to manually create pairings.