We've sorted out most of our error handling by now with manual catches. However every now and then we find a weird edgecase like a random api call fail that was unexpected and the frontend explodes.
We should have a general error catcher on the api level which if a request fails simply shows a toast/error message and aborts further code execution. This will prevent ugly ui degradation in case something odd happens while users are playing around.
chriswhong
commented
2 years ago
We've sorted out most of our error handling by now with manual catches. However every now and then we find a weird edgecase like a random api call fail that was unexpected and the frontend explodes.
We should have a general error catcher on the api level which if a request fails simply shows a toast/error message and aborts further code execution. This will prevent ugly ui degradation in case something odd happens while users are playing around.