Lobby component receives user list in state, so all that needs to be added is a ui component to display that data.

To see if it's for the appropriate game

This is all set up in the backend. React should listen for CLIENT CONNECT ACK and then switch to the login page IF they're not already there (we don't want an infinite loop).

Changed backend feed message logic so that the data field returns null when the message isn't a valid or invalid set. When it is set-related, it contains an array of cards that should show up as small icons next to the message

The Java server crashes occasionally when a logged in client reconnects and then tries to log back in. This is probably due to client disconnect not actually "logging out" a user on the Java side.
Update: This seems to happen on the LOBBY LIST message from the client.

Keep a logged in flag in the DB

Submitting a set successfully does not allow any other cards to be selected. This seems like it has something to do with the number of selected cards not getting updated in the submitSet callback.

"Join finished game" or something

• Delete button in Lobby
• Start button in game

When the GAME JOIN command fails, the join button doesn't ever leave the loading state. Seems like this should happen on GAME JOIN ACK, false.

• Remove active state
• Animate red if < 3 cards selected
• Animate green when successfully submttted?

There is an issue in node where it gets a message from the java and randomly crash because of a JSON.parse issue (unexpected token {). This is rampant and keeps happening, which is keeping us from testing thoroughly.

So I played a game and my score was 9
I left game and joined a new one
My score was still 9
😢

Maybe on top of the board?

It's a mess with LOBBY LIST and LOBBY UPDATE SUCCESS. Maybe a subscribe method like for games.

Get on it

Have different styles for each message type (colors, fonts, etc). Also change the style of the username.

Also might not have to - just need to wait until functionality is complete to see how react behaves.

There are instances of the system where disconnected a client throws a Concurrent Modification Exception on CLIENT DISCONNECT. This seems to be happening in the games HashMap in Lobby.java. This issue occurred when dealing with game deletion with multiple users in the lobby (exact circumstances unclear).

• Log in
• Refresh
• Crash

There is no condition in React that checks whether a set is successful or not. It just logs a message. There should be some sort of indicator (just to the submitting user) that things worked (other than just the score update).

{
user: 'username',
id: xx
}

When there's no set on the board, extra cards are added (15, 18). The board size needs to go back down once there's a set available in just 12 cards.