[MGNLUI-6396] Throw more human readable error messages instead of uninformative exceptions Created: 10/Nov/20 Updated: 10/Mar/21 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Neutral |
| Reporter: | Šimon Demočko | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Epic Name: | Human readable errors |
| Acceptance criteria: |
Empty
|
| Description |
Current situationIn many situations, the user is faced with exceptions with little additional information. They do not know what caused a problem, they do not know what information to pass on to the administrator and the situation is quite unprofessional sometimes with stack traces in a foreign language. See example steps to reproduce below. Desired situationIn this old page there was this agreement, without associated Jira ticket
Another thing to consider is to throw custom Magnolia Exceptions so we can distinguish exceptions that we know hold the information we want to show to the user eventually (localized) Example Steps to reproduceGo to JCR Browser and attempt to export any contact. Actual resultRed banner ** is shown with message "An error occurred while executing an action." with description "Action execution failed for action: export" Expected resultA popup, notification, or error banner with a meaningful user-facing maybe even translated message that helps the user understand the problem and point him to a solution or to whom they should turn with questions. |