error-handling

Handling SDK error responses in a TypeScript frontend requires discriminating between IErrorResponse objects and thrown errors to prevent silent failures. This approach provides strategies to correctly process these distinct Nuclia SDK response types.

Showing toast notifications for RxJS error handling in Angular involves integrating SisToastService with i18n keys to display user-friendly messages. This ensures consistent error surfacing across the application instead of silent failures.

The catchError operator often fails when sharing RxJS streams because incorrect shareReplay ordering disrupts the pipeline lifecycle. Addressing this ordering ensures proper error propagation and prevents redundant subscriptions from swallowing exceptions.

You do not need to manually handle 401 authentication errors if an AuthInterceptor is already implemented. The interceptor manages these requests centrally, and adding manual checks creates redundant error handling logic in your components.

Implementing retry logic for rate-limited requests in an SDK involves using standardized retry configuration helpers provided by the framework. This standardizes the backoff strategy for uploads and prevents immediate request flooding.

You can use the same error handling patterns for Svelte and React components by applying specific UI error state strategies. This approach demonstrates how to surface SDK errors consistently across both Svelte search-widgets and React rao-widgets.