You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: