Cache driver lookup in /me controller routes #20

New Issue

kyle · 2026-02-08T06:44:20-08:00

kyle commented

2026-02-08 06:44:20 -08:00

Context: The drivers controller has multiple /me/* routes that each independently call findByUserId() to resolve the current driver. When a driver hits several of these endpoints, the same lookup runs repeatedly.

File: backend/src/drivers/drivers.controller.ts (lines 44-49, 58-75, 83-100, 112-131)

Suggested fix:

Create a @CurrentDriver() param decorator (similar to @CurrentUser()) that resolves the driver once per request via middleware or interceptor
Or use a request-scoped cache so findByUserId() result is reused within the same request lifecycle

Effort: Small

**Context:** The drivers controller has multiple `/me/*` routes that each independently call `findByUserId()` to resolve the current driver. When a driver hits several of these endpoints, the same lookup runs repeatedly. **File:** `backend/src/drivers/drivers.controller.ts` (lines 44-49, 58-75, 83-100, 112-131) **Suggested fix:** - Create a `@CurrentDriver()` param decorator (similar to `@CurrentUser()`) that resolves the driver once per request via middleware or interceptor - Or use a request-scoped cache so `findByUserId()` result is reused within the same request lifecycle **Effort:** Small

kyle referenced this issue

2026-02-08 06:44:30 -08:00

Code Efficiency #8

kyle referenced this issue from a commit

2026-02-08 07:07:27 -08:00

refactor: code efficiency improvements (Issues #9-13, #15, #17-20)

kyle commented

2026-02-08 07:09:58 -08:00

Created decorator and . Updated drivers controller /me routes to use single lookup.

kyle closed this issue

2026-02-08 07:09:59 -08:00

Sign in to join this conversation.