As of right now, any calls to our API is done via 1 connection to the MySQL. As such, if that connection disconnects (which it automatically does, around 8 hours of non-use), it is possible to crash the backend server if someone tries to make a call to the server while there isn't a connection.
These changes fixes that problem by adding a middleware to the POST server.ts calls, which basically checks if there exists a MySQL connection before actually going through with the request. If the connection is offline, it will automatically boot it back up before making the call, which prevents the potential for crashes in this scenario.
I also updated package.json to include graphql as a dependency so the backend server can install it (graphql is required to get RMP data)
This highlights a standard we need to follow: always try/catch any potential for errors so the backend server doesn't die. Thanks for coming to my ted talk
As of right now, any calls to our API is done via 1 connection to the MySQL. As such, if that connection disconnects (which it automatically does, around 8 hours of non-use), it is possible to crash the backend server if someone tries to make a call to the server while there isn't a connection.
This highlights a standard we need to follow: always try/catch any potential for errors so the backend server doesn't die. Thanks for coming to my ted talk