What is the binding order precedence when the same enhancer type is applied at global, controller, and method level in NestJS?

Q: What is the binding order precedence when the same enhancer type is applied at global, controller, and method level in NestJS?

// A request to GET /users/:id runs guards in this order: // 1. GlobalAuthGuard (registered via APP_GUARD) // 2. ControllerRolesGuard (@UseGuards on the class) // 3. MethodThrottleGuard (@UseGuards on the method) @UseGuards(ControllerRolesGuard) @Controller('users') export class UsersController { @UseGuards(MethodThrottleGuard) @Get(':id') findOne() {} } Guards — global → controller → method. All must return true for the request to proceed. Interceptors — global → controller → method (pre). Reverse on the way out (post). Pipes — global → controller → method. Each pipe runs on its bound parameter. Exception filters — method → controller → global. First matching @Catch() type wins. The filter reversal is the most commonly confused rule — remember: most specific filter wins.

Difficulty: 5/10

enhancer precedence, global vs controller vs method, NestJS lifecycle

For guards, interceptors, and pipes the execution order is global → controller → method. For exception filters the resolution order inverts: method → controller → global. The first filter whose @Catch() type matches the thrown exception handles it.

Guard execution order across binding levels

Precedence rules by enhancer type:

1
Guards — global → controller → method. All must return true for the request to proceed.
2
Interceptors — global → controller → method (pre). Reverse on the way out (post).
3
Pipes — global → controller → method. Each pipe runs on its bound parameter.

What is the binding order precedence when the same enhancer type is applied at global, controller, and method level in NestJS?

Difficulty: 5/10

enhancer precedence, global vs controller vs method, NestJS lifecycle

For guards, interceptors, and pipes the execution order is global → controller → method. For exception filters the resolution order inverts: method → controller → global. The first filter whose @Catch() type matches the thrown exception handles it.

Guard execution order across binding levels

Precedence rules by enhancer type:

1
Guards — global → controller → method. All must return true for the request to proceed.
2
Interceptors — global → controller → method (pre). Reverse on the way out (post).
3
Pipes — global → controller → method. Each pipe runs on its bound parameter.

What is the binding order precedence when the same enhancer type is applied at global, controller, and method level in NestJS?

For guards, interceptors, and pipes the execution order is global → controller → method. For exception filters the resolution order inverts: method → controller → global. The first filter whose @Catch() type matches the thrown exception handles it.

What is the binding order precedence when the same enhancer type is applied at global, controller, and method level in NestJS?

For guards, interceptors, and pipes the execution order is global → controller → method. For exception filters the resolution order inverts: method → controller → global. The first filter whose @Catch() type matches the thrown exception handles it.

Scenario Questions

Follow-up Questions