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
{{ message }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
When an exception is raised, we catch it and send it to the server. But we didn't provide any feedback to the user. The exception often means that the user attempted an action that failed, and he didn't get any feedback. This is really frustrating. So, when an exception is thrown, we should notify the user (and maybe suggest to use the contact form to explain how to reproduce the issue ? When we see error stack on server side, we often miss context.)
The text was updated successfully, but these errors were encountered:
When an exception is raised, we catch it and send it to the server. But we didn't provide any feedback to the user. The exception often means that the user attempted an action that failed, and he didn't get any feedback. This is really frustrating. So, when an exception is thrown, we should notify the user (and maybe suggest to use the contact form to explain how to reproduce the issue ? When we see error stack on server side, we often miss context.)
The text was updated successfully, but these errors were encountered: