fix(shared): handle Prisma errors in GlobalExceptionFilter to return proper HTTP status codes

Browse Source

Prisma errors (P2025 record not found, P2002 unique constraint, P2003 foreign key)
were falling through to the catch-all handler and returning 500 Internal Server Error
instead of appropriate 404/409/400. This caused GET /listings/:id with a non-existent
ID to return 500 when the Prisma layer threw before the application null check.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

...

This commit is contained in:

Ho Ngoc Hai

2026-04-10 21:21:25 +07:00

parent d30c5630ce

commit 783b5b74f1

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available