angular-error-handling

Standard IDs

ID	Severity	What it checks
AEH-001	P1	No global ErrorHandler registered for uncaught exceptions
AEH-002	P2	Per-component ad-hoc catchError with no shared error-boundary/notification pattern
AEH-003	P1	HTTP error responses not parsed against the .NET ProblemDetails shape
AEH-004	P2	No user-facing fallback UI distinguishing a recoverable error from a full crash

---

Check A — No global ErrorHandler (AEH-001)

Detection

Check app.config.ts/AppModule providers for a custom ErrorHandler implementation. Without one, an uncaught exception anywhere in the component tree (a template expression throwing, an unguarded array access) surfaces only in the browser console — the user sees a frozen or partially-rendered page with no indication anything went wrong.

BAD — no global ErrorHandler, uncaught exceptions vanish into the console

export const appConfig: ApplicationConfig = {
  providers: [provideHttpClient(), provideRouter(routes)],
  // No ErrorHandler override — Angular's default just console.errors and moves on.
};

GOOD — a global ErrorHandler that logs and surfaces a recoverable notification

@Injectable()
export class GlobalErrorHandler implements ErrorHandler {
  private readonly notifications = inject(NotificationService);
  private readonly telemetry = inject(TelemetryService);

  handleError(error: unknown): void {
    this.telemetry.trackException(error); // send to Application Insights JS SDK
    this.notifications.showError('Something went wrong. Please try again.');
  }
}

export const appConfig: ApplicationConfig = {
  providers: [{ provide: ErrorHandler, useClass: GlobalErrorHandler }],
};

---

Check B — Ad-hoc catchError with no shared pattern (AEH-002)

Detection

Grep components/services for repeated catchError(err => { /* custom toast logic */ }) blocks that each reimplement how an HTTP failure is surfaced to the user, instead of one shared error-normalization interceptor/service reused everywhere (this builds on angular-http-resilience's error-normalization guidance, applied consistently at the UI layer, not just the data layer).