angular-fullstack/generator-angular-fullstack

Unified error handling

Open

#1502 opened on Dec 17, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (6,134 stars) (1,268 forks)batch import
Help Wantedenhancement

Description

The error handling is not DRY - it'd be great to use .catch(next) and have a centralised error middleware. Would save 1000s of LOC in larger projects!

Contributor guide

Tech stack
javascriptnodejsexpress
Domain
backendapi
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of ExpressJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue requests implementing centralized error handling using Express error middleware and the `.catch(next)` pattern. Relevant files are the Express server setup (likely `server.js` or `app.js`) and any existing route handlers. First, create a custom error class and an error handling middleware with signature `(err, req, res, next)`. Then, modify route handlers to use `catch(next)` to forward errors. Refer to Express error handling documentation for details. Since the issue is from 2015 and the project may be outdated, check if the current codebase still uses Express and if there are any existing error handling approaches.