error-handling

Map exceptions to a consistent ApiErrorResponse across NestJS controllers, use-case services, and infrastructure adapters to ensure uniform API error payloads. Structured error mapping eliminates inconsistent failure diagnostics.

NestJS exception handling categorizes failures into UsecaseException, InfrastructureException, DomainException, ThirdPartyException, and I18nValidationException. Each exception type maps to a structured ApiErrorResponse for consistent client feedback.

Trigger Telegram alerts for critical NestJS failures by configuring interceptor-driven logging and tracing. The TransformUseSentryInterceptor and ExceptionInterceptor automatically dispatch notifications when critical exceptions occur.

Stack traces are stripped in production to secure API error payloads. The error handling mechanism ensures sensitive debugging details remain internal while returning clean ApiErrorResponse objects to clients.

Configure TransformUseSentryInterceptor and ExceptionInterceptor in AppModule to enable NestJS error handling. Throw UsecaseException, InfrastructureException, or DomainException to verify standardized API responses.

RPC adapters and fallback handlers ensure uniform error semantics across microservice boundaries and external calls. This maintains consistent API error payloads even when failures occur in remote service interactions.