Table of Contents
What is Angular
try/catch
ErrorHandler
HttpInterceptor
Notifications
Of course the user cannot be expected to report to Per
Home Web Front-end JS Tutorial One article to understand how to handle errors in Angular

One article to understand how to handle errors in Angular

Jun 29, 2021 am 10:51 AM
angular Error handling

How can errors be handled in

Angular? This article will take you through the error handling mechanism in Angular and introduce how to handle errors.

One article to understand how to handle errors in Angular

Error handling is a requirement that is often encountered when writing code and must be handled. Many times the logic of handling exceptions is to avoid program crashes. Let’s take a look at it AngularHow to handle errors. [Related tutorial recommendations: "angular tutorial"]

What is Angular

Angualr is a tool from Google The open source web front-end framework was born in 2009, created by Misko Hevery and others, and later acquired by Google. It is an excellent front-end JS framework that has been used in many Google products.

AngularJS is based on the declarative programming model so that users can develop based on business logic. The framework is based on HTML content filling and two-way data binding to complete the automatic data synchronization mechanism. Finally, AngularJS Enhanced DOM operations enhance testability.

try/catch

The most familiar way is to add try/ in the code catch block, if an error occurs in try, it will be caught and the script will continue to execute. However, as the size of the application increases, this approach becomes unmanageable.

ErrorHandler

Angular provides a default ErrorHandler that prints error messages to the console, so you can Intercept this default behavior to add custom processing logic. Try writing an error handling class below:

import { ErrorHandler, Injectable } from "@angular/core";
import { HttpErrorResponse } from "@angular/common/http";

@Injectable()
export class ErrorsHandler implements ErrorHandler {
  handleError(error: Error | HttpErrorResponse) {
    if (!navigator.onLine) {
      console.error("Browser Offline!");
    } else {
      if (error instanceof HttpErrorResponse) {
        if (!navigator.onLine) {
          console.error("Browser Offline!");
        } else {
          // Handle Http Error (4xx, 5xx, ect.)
          console.error("Http Error!");
        }
      } else {
        // Handle Client Error (Angular Error, ReferenceError...)
        console.error("Client Error!");
      }
      console.error(error);
    }
  }
}
Copy after login

Usually create a shared directory under appshared , and place this file in the providers folder

Now, we need to change the default behavior of the application to use our custom class instead of ErrorHandler. Modify the app.module.ts file, import ErrorHandler from @angular/core, and add providers to @NgModule Module, the code is as follows:

import { NgModule, ErrorHandler } from "@angular/core";
import { BrowserModule } from "@angular/platform-browser";
import { FormsModule } from "@angular/forms";

// Providers
import { ErrorsHandler } from "./shared/providers/error-handler";

import { AppComponent } from "./app.component";

@NgModule({
  imports: [BrowserModule, FormsModule],
  declarations: [AppComponent],
  providers: [{ provide: ErrorHandler, useClass: ErrorsHandler }],
  bootstrap: [AppComponent]
})
export class AppModule {}
Copy after login

HttpInterceptor

##HttpInterceptor provides a interception of HTTP requests/responses methods, they can be processed before passing them. For example, an HTTP request can be retried several times before an error is thrown. This way, timeouts can be handled gracefully without having to throw errors.

You can also check the error status before throwing the error. Using an interceptor, you can check the 401 status error code and redirect the user to the login page.

import { Injectable } from "@angular/core";
import { HttpEvent, HttpRequest, HttpHandler, HttpInterceptor, HttpErrorResponse } from "@angular/common/http";
import { Observable, throwError } from "rxjs";
import { retry, catchError } from "rxjs/operators";

@Injectable()
export class HttpsInterceptor implements HttpInterceptor {
  intercept(request: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
    return next.handle(request).pipe(
      retry(1),
      catchError((error: HttpErrorResponse) => {
        if (error.status === 401) {
          // 跳转到登录页面
        } else {
          return throwError(error);
        }
      })
    );
  }
}
Copy after login

also needs to be added to

app.module.ts

import { NgModule, ErrorHandler } from "@angular/core";
import { HTTP_INTERCEPTORS } from "@angular/common/http";
import { BrowserModule } from "@angular/platform-browser";
import { FormsModule } from "@angular/forms";

// Providers
import { ErrorsHandler } from "./shared/providers/error-handler";
import { HttpsInterceptor } from "./shared/providers/http-interceptor";

import { AppComponent } from "./app.component";

@NgModule({
  imports: [BrowserModule, FormsModule],
  declarations: [AppComponent],
  providers: [
    { provide: ErrorHandler, useClass: ErrorsHandler },
    { provide: HTTP_INTERCEPTORS, useClass: HttpsInterceptor, multi: true }
  ],
  bootstrap: [AppComponent]
})
export class AppModule {}
Copy after login

Multiple providers are used to create extensible services, in which the system comes with some default providers , you can also sign up for other providers. A combination of the default provider and other providers will be used to drive the behavior of the system.

Notifications

Printing error logs on the console is very friendly to developers, but for users, a more friendly way is needed. Tell when these errors occur from the GUI. Depending on the error type, two components are recommended:

Snackbar and Dialog

  • ##Snackbar

    : Recommended for simple prompts , such as a form missing a required field or notifying the user of predictable errors (invalid email, username too long, etc.).

  • Dialog

    : This method is recommended when there are unknown server-side or client-side errors; in this way, more descriptions can be displayed, Or even call-to-action, like allowing users to enter their email to track bugs.

  • Add a service in the
shared

folder to handle all notifications, create a new services folder, and create the file: notification. service.ts, the code is as follows: <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>import { Injectable } from &quot;@angular/core&quot;; import { MatSnackBar } from &quot;@angular/material/snack-bar&quot;; @Injectable({ providedIn: &quot;root&quot; }) export class NotificationService { constructor(public snackBar: MatSnackBar) {} showError(message: string) { this.snackBar.open(message, &quot;Close&quot;, { panelClass: [&quot;error&quot;] }); } }</pre><div class="contentsignin">Copy after login</div></div>Update

error-handler.ts

, add NotificationService: <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>import { ErrorHandler, Injectable, Injector } from &quot;@angular/core&quot;; import { HttpErrorResponse } from &quot;@angular/common/http&quot;; // Services import { NotificationService } from &quot;../services/notification.service&quot;; @Injectable() export class ErrorsHandler implements ErrorHandler { //Error handling需要先加载,使用Injector手动注入服务 constructor(private injector: Injector) {} handleError(error: Error | HttpErrorResponse) { const notifier = this.injector.get(NotificationService); if (!navigator.onLine) { //console.error(&quot;Browser Offline!&quot;); notifier.showError(&quot;Browser Offline!&quot;); } else { if (error instanceof HttpErrorResponse) { if (!navigator.onLine) { //console.error(&quot;Browser Offline!&quot;); notifier.showError(error.message); } else { // Handle Http Error (4xx, 5xx, ect.) // console.error(&quot;Http Error!&quot;); notifier.showError(&quot;Http Error: &quot; + error.message); } } else { // Handle Client Error (Angular Error, ReferenceError...) // console.error(&quot;Client Error!&quot;); notifier.showError(error.message); } console.error(error); } } }</pre><div class="contentsignin">Copy after login</div></div>If in a component When an error is thrown in, you can see a nice

snackbar

message:

Logs and Error Tracing

Of course the user cannot be expected to report to Per

bug

, once deployed to production, no console logs can be seen. Therefore, you need a backend service that can log errors with custom logic written to the database or use existing solutions such as Rollbar, Sentry, Bugsnag. Next create a simple error tracking service, create

logging.service.ts

: <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>import { Injectable } from &quot;@angular/core&quot;; import { HttpErrorResponse } from &quot;@angular/common/http&quot;; @Injectable({ providedIn: &quot;root&quot; }) export class LoggingService { constructor() {} logError(error: Error | HttpErrorResponse) { // This will be replaced with logging to either Rollbar, Sentry, Bugsnag, ect. if (error instanceof HttpErrorResponse) { console.error(error); } else { console.error(error); } } }</pre><div class="contentsignin">Copy after login</div></div>Add the service to

error-handler.ts

中:

import { ErrorHandler, Injectable, Injector } from "@angular/core";
import { HttpErrorResponse } from "@angular/common/http";
// Services
import { NotificationService } from "../services/notification.service";
import { LoggingService } from "../services/logging.service";

@Injectable()
export class ErrorsHandler implements ErrorHandler {
  //Error handling需要先加载,使用Injector手动注入服务
  constructor(private injector: Injector) {}
  handleError(error: Error | HttpErrorResponse) {
    const notifier = this.injector.get(NotificationService);
    const logger = this.injector.get(LoggingService);
    if (!navigator.onLine) {
      //console.error("Browser Offline!");
      notifier.showError("Browser Offline!");
    } else {
      if (error instanceof HttpErrorResponse) {
        if (!navigator.onLine) {
          //console.error("Browser Offline!");
          notifier.showError(error.message);
        } else {
          // Handle Http Error (4xx, 5xx, ect.)
          // console.error("Http Error!");
          notifier.showError("Http Error: " + error.message);
        }
      } else {
        // Handle Client Error (Angular Error, ReferenceError...)
        // console.error("Client Error!");
        notifier.showError(error.message);
      }
      // console.error(error);
      logger.logError(error);
    }
  }
}
Copy after login
So far, the entire error handling mechanism has been introduced, which is basically similar to the way projects developed in other frameworks or languages ​​are handled.

For more programming-related knowledge, please visit: Introduction to Programming! !

The above is the detailed content of One article to understand how to handle errors in Angular. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Using middleware to improve error handling in golang functions Using middleware to improve error handling in golang functions Apr 24, 2024 pm 06:57 PM

Use middleware to improve error handling in Go functions: Introducing the concept of middleware, which can intercept function calls and execute specific logic. Create error handling middleware that wraps error handling logic in a custom function. Use middleware to wrap handler functions so that error handling logic is performed before the function is called. Returns the appropriate error code based on the error type, улучшениеобработкиошибоквфункциях Goспомощьюпромежуточногопрограммногообеспечения.Оно позволяетнамсосредоточитьсянаобработкеошибо

How to effectively handle error scenarios in C++ through exception handling? How to effectively handle error scenarios in C++ through exception handling? Jun 02, 2024 pm 12:38 PM

In C++, exception handling handles errors gracefully through try-catch blocks. Common exception types include runtime errors, logic errors, and out-of-bounds errors. Take file opening error handling as an example. When the program fails to open a file, it will throw an exception and print the error message and return the error code through the catch block, thereby handling the error without terminating the program. Exception handling provides advantages such as centralization of error handling, error propagation, and code robustness.

Best tools and libraries for PHP error handling? Best tools and libraries for PHP error handling? May 09, 2024 pm 09:51 PM

The best error handling tools and libraries in PHP include: Built-in methods: set_error_handler() and error_get_last() Third-party toolkits: Whoops (debugging and error formatting) Third-party services: Sentry (error reporting and monitoring) Third-party libraries: PHP-error-handler (custom error logging and stack traces) and Monolog (error logging handler)

How to perform error handling and logging in C++ class design? How to perform error handling and logging in C++ class design? Jun 02, 2024 am 09:45 AM

Error handling and logging in C++ class design include: Exception handling: catching and handling exceptions, using custom exception classes to provide specific error information. Error code: Use an integer or enumeration to represent the error condition and return it in the return value. Assertion: Verify pre- and post-conditions, and throw an exception if they are not met. C++ library logging: basic logging using std::cerr and std::clog. External logging libraries: Integrate third-party libraries for advanced features such as level filtering and log file rotation. Custom log class: Create your own log class, abstract the underlying mechanism, and provide a common interface to record different levels of information.

Asynchronous processing in golang function error handling Asynchronous processing in golang function error handling May 03, 2024 pm 03:06 PM

In Go functions, asynchronous error handling uses error channels to asynchronously pass errors from goroutines. The specific steps are as follows: Create an error channel. Start a goroutine to perform operations and send errors asynchronously. Use a select statement to receive errors from the channel. Handle errors asynchronously, such as printing or logging error messages. This approach improves the performance and scalability of concurrent code because error handling does not block the calling thread and execution can be canceled.

Error handling strategies for Go function unit testing Error handling strategies for Go function unit testing May 02, 2024 am 11:21 AM

In Go function unit testing, there are two main strategies for error handling: 1. Represent the error as a specific value of the error type, which is used to assert the expected value; 2. Use channels to pass errors to the test function, which is suitable for testing concurrent code. In a practical case, the error value strategy is used to ensure that the function returns 0 for negative input.

Best practices for error handling in golang functions Best practices for error handling in golang functions Apr 24, 2024 pm 05:24 PM

Best practices for error handling in Go include: using the error type, always returning an error, checking for errors, using multi-value returns, using sentinel errors, and using error wrappers. Practical example: In the HTTP request handler, if ReadDataFromDatabase returns an error, return a 500 error response.

How to use Golang's error wrapper? How to use Golang's error wrapper? Jun 03, 2024 pm 04:08 PM

In Golang, error wrappers allow you to create new errors by appending contextual information to the original error. This can be used to unify the types of errors thrown by different libraries or components, simplifying debugging and error handling. The steps are as follows: Use the errors.Wrap function to wrap the original errors into new errors. The new error contains contextual information from the original error. Use fmt.Printf to output wrapped errors, providing more context and actionability. When handling different types of errors, use the errors.Wrap function to unify the error types.

See all articles