Improve error handling

[joshuawilson]

From @joshuawilson on August 17, 2017 17:10

We have observed that some errors can break whole sections of the UI when they really should be isolated.

We need to look at improving our error handling locally and consider covering global error handling.

This article is a starting point. https://medium.com/@amcdnl/global-error-handling-with-angular2-6b992bdfb59c

Copied from original issue: fabric8-ui/fabric8-ui#1885

[joshuawilson]

From @dgutride on August 17, 2017 17:13

One other thing we could consider is uploading exceptions to a common logging endpoint to trigger quick responses (and reporting). We might need a design for error handling in the UI - should we show a notification, always redirect to an error page, let the user continue working? We can't guarantee an unhandled exception will still result in a usable page for users but there is a possibility they can still move forward with limited functionality.

[joshuawilson]

I have talked about posting UI errors back to the server so they can be viewed in logs and error tracking software we use. This would allow us to spot errors that users are seeing before they report them.