A topic that came up in the Support SIG:
- Users are sometimes encountering nasty stack trace error messages when Stripes / React.js exceptions are not caught. Browser error messages should be more explicit and robust. Is there a way to standardize or even automate that?
- This example SUP-17 occurred resulting in the current page becoming unstable (The message only refers to the browser’s state, not the system back end’s state).
- Ingolf also encounters this type of error, after having created a new object via the API. A page reload removes the error message (and the problem). The users shouldn't have to do a page refresh, of course.
- Julian says these are programming errors in the frontend. He says, a Jira ticket has to be created for each of them, like in this list
| type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
- The SIG believes that robust, descriptive error messages are ideal, in helping resolve issues. However, there are layers of abstraction that don't provide helpful information. The logs should have the details, and the front end should handle errors more gracefully to improve the user experience. There may not be a technical solution to deal with this globally, but there should be a best practice around this.
- Tod offered to bring up this issue to the Tech Council. Phil will provide him a brief writeup.