Open chbfiv opened 10 years ago
Related to the match design let's say we fetch and store the moves with that match object. The get moves call can get all or the last n moves. There was a request by a developer to be able to quickly determine who made which move, so was thinking we could have a list of move objects with one field being the user who made the move, but if the move data wasn't fetched that would just be null or with a flag that says fetched.
improve match design. Suggested: 1) one match list with iterators for your turn, their turn, and completed 2) separate your turn, their turn, and completed match list
get moves to be done on the "match" object