Angular error handling best practices

#ngKeralam - Angular conference 2022

Transcript

1. Angular error handling Pandiyan Murugan - 29-Jan-22 Best practices
2. Backstory of an error • Complexity of application • Communication between stakeholders • Developer mistakes • Time pressure • Lack of testing
3. catch?
5. Catch them all • Angular provides a hook for centralized exception handling with ErrorHandler. • However, the default implementation of ErrorHandler only prints error messages to the console. We can modify later.
6. • Then, we provide it in our root module to change default behavior in our application. Instead of using the default ErrorHandler class we are using our class
7. Errors • Client side errors • Server side errors •
8. Error service
9. HttpInterceptor • HttpInterceptor was introduced with Angular 4.3.1. It provides a way to intercept HTTP requests and responses to transform or handle them before passing them along. •
10. Demo • https://stackblitz.com/edit/angular-ivy-mym3tm? file=src%2Fapp%2Fapp.component.ts
11. References • https://indepth.dev/posts/1465/expecting-the-unexpected-best-practices- for-error-handling-in-angular-2 • https://itnext.io/how-to-handle-your-run-time-errors-in-your-angular- application-8d72fefbf8a4 •