Returns 201 if userActiveGameService is successful Otherwise catches error and sends to our errorHandler Takes sanitized input and sends it to userActiveGamesService
This is the request object
This is the response object
This takes us to the errorHandler if request fails
Returns 200 if userGameStatisticsService is successful Otherwise catches error and sends to our errorHandler Takes sanitized input and sends it to userGameStatisticsService
This is the request object
This is the response object
This takes us to the errorHandler if request fails
Returns 200 if userActiveGameService is successful Otherwise catches error and sends to our errorHandler Takes sanitized input and sends it to userActiveGamesService
This is the request object
This is the response object
This takes us to the errorHandler if request fails
Returns 200 if userActiveGamesService is successful Otherwise catches error and sends to our errorHandler Takes sanitized input and sends it to userActiveGamesService
This is the request object
This is the response object
This takes us to the errorHandler if request fails
Generated using TypeDoc
This is the controller file for the puzzle endpoint This file is called by the router file and calls the service file There are four main functions createUserGameStatistics, searchUserGameStatistics, updateUserGameStatistics, and removeUserGameStatistics The main purpose of the controller is to make sure that only validated and sanitized data moves on to the service function