Errors can come from many different sources - third-party services, libraries, environment, etc. When an error prevents a user from performing their desired action, these diverse errors should be communicated to the user, so they their action failed and can take steps to solve the issue.Are there any common strategies for normalizing diverse errors? As an example scenario, imagine an application that consumes data from the local machine, a database, and a third-party web service. This application provides some kind of user interface (CLI, web app, desktop app, etc.), and when an error occurs it informs the user.In my mind, the key issues are:Handling errors consistentlyEffectively communicating error to users and to developersA good answer would be something like a common pattern, a sample implementation, technical overview, or something more broad like a link to a popular video on the subject.
Handling and reporting errors consistently
web applications;user interface;error handling;logging;services