@gram-ai/elements 1.20.1 → 1.20.2

package/dist/components/Chat/stories/ErrorBoundary.stories.d.ts

@@ -0,0 +1,8 @@
+import { Meta, StoryFn } from '@storybook/react-vite';
+import { Chat } from '..';
+declare const meta: Meta<typeof Chat>;
+export default meta;
+type Story = StoryFn<typeof Chat>;
+export declare const Modal: Story;
+export declare const Standalone: Story;
+export declare const Sidecar: Story;

package/dist/components/assistant-ui/error-boundary.d.ts

@@ -0,0 +1,28 @@
+import { Component, ErrorInfo, ReactNode } from 'react';
+interface ErrorBoundaryProps {
+    children: ReactNode;
+    fallback?: ReactNode;
+    onError?: (error: Error, errorInfo: ErrorInfo) => void;
+    onReset?: () => void;
+}
+interface ErrorBoundaryState {
+    hasError: boolean;
+    error: Error | null;
+    resetKey: number;
+}
+/**
+ * Global error boundary for the Elements library. Catches unexpected errors and renders a fallback UI.
+ * We wrap the assistant-modal, assistant-sidecar, and chat components with this error boundary.
+ * Each variant needs to have the error boundary rendered at the appropriate level e.g if using
+ * the widget variant, then the error screen must be rendered within the widget modal.
+ * TODO: We should add more granular error boundaries (e.g wrapping AssistantMessage, ThreadWelcome, etc.)
+ * TODO: We should also wrap ChatHistory, which may yield its own errors.
+ */
+export declare class ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {
+    constructor(props: ErrorBoundaryProps);
+    static getDerivedStateFromError(error: Error): Partial<ErrorBoundaryState>;
+    componentDidCatch(error: Error, errorInfo: ErrorInfo): void;
+    handleRetry: () => void;
+    render(): ReactNode;
+}
+export {};