Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

Match allocation edge cases #119

Open
NWKendall opened this issue Apr 24, 2020 · 0 comments
Open

Match allocation edge cases #119

NWKendall opened this issue Apr 24, 2020 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@NWKendall
Copy link
Contributor

NWKendall commented Apr 24, 2020

Currently, the matchMaking and versusRoutes endpoints handle matchmaking for four individuals, 2 teams of 2 correctly.

Although DS will allocate players to matches with less than 4 players, BE cannot dynamically handle matches if one, two or three players are left out, or what to do if child.id = 0 is present in a match object.

Possibly 2 vs 1 scenario, 1 vs 1 scenario, or duplicate some submissions to be used multiple times to fill in for the missing players.

*Stakeholder aware of issue

@NWKendall NWKendall added bug Something isn't working help wanted Extra attention is needed labels Apr 24, 2020
@NWKendall NWKendall changed the title #104 Match allocation edge cases Match allocation edge cases Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant