Issue 25: Game Integration

[darrenMabbayad]

#25, #12, #29, #35, #36

This PR addresses several issues

Game Integration

• all game events handled through socket events in GameplayContext,js and /server/sockets.js
• game flow is as follows:
  start game
  send clues
  change game phase to guessing phase
  send guess
  check answer and clues, distribute points, move to next round
  when 4 rounds have passed, game ends
  save game data to mongoDB when host leaves

Match Management/Socket IO

• all matches are handled with MatchManager.js, /server/sockets.js, Game.js, GameContext.js, GamePlayContext.js
• create match sends request to /game/create, creates match in MongoDB, adds user to player list and tags the creator as host
• join match sends request to /game/:gameId/join, adds player with Joined status in MongoDB, adds user to player list
• important data concerning a Match instance is handled in memory (player points, who the guesser is, current round, clues submitted, typing status, etc.)

Socket IO security

• added socket.io middleware for authentication io.use()
• verify JWT on initial socket connection (using jsonwebtoken library)
• if authentication error or user is unauthorized, remove local storage user, set auth to false, return to login

Game Audio

• use HowlerJS library to generate sound effects on certain game events
• static game audio files are in /client/src/game-audio
• audio is emitted to every user on sockets events: 'FE-send-clue' and 'FE-send-answer'

Responsive Design

• routes for /create-game and /lobby are now suitable for mobile