At the moment, it can be unclear why the website has failed to process a request / doesn't work
e.g. Is the user disconnected from internet? Is the server down for maintenance, etc...
Therefore, we should improve the toast error messages beyond "Connection Failure".
We should use the window.onLine api to test if a user has internet connection and display a more informative error message such as "Connection Failure. Please check your internet connection." if the user doesn't have internet.
We should also make a query to the api's status endpoint to check if the server is down for maintenance.
Additional Information
This has been a pain point for users as the client is semi-usable without an internet connection (after initial page load). Causing them to think that the server is down.
At the moment, it can be unclear why the website has failed to process a request / doesn't work e.g. Is the user disconnected from internet? Is the server down for maintenance, etc...
Therefore, we should improve the toast error messages beyond "Connection Failure".
We should use the window.onLine api to test if a user has internet connection and display a more informative error message such as "Connection Failure. Please check your internet connection." if the user doesn't have internet.
We should also make a query to the api's
statusendpoint to check if the server is down for maintenance.Additional Information
This has been a pain point for users as the client is semi-usable without an internet connection (after initial page load). Causing them to think that the server is down.
Related to: #205