xertica-ui 2.4.0 → 2.4.1

package/components/shared/error-boundary.stories.tsx

@@ -1,114 +1,114 @@
-import type { Meta, StoryObj } from '@storybook/react';
-import React, { useState } from 'react';
-import { AppErrorBoundary, PageErrorBoundary, SectionErrorBoundary } from './error-boundary';
-
-// ── Crash helper ─────────────────────────────────────────────────────────────
-// A component that throws on the next render when `shouldCrash` is true.
-// Used in every story to demonstrate real boundary behaviour.
-
-function Crashable({ shouldCrash, label }: { shouldCrash: boolean; label: string }) {
-  if (shouldCrash) throw new Error(`Simulated crash in: ${label}`);
-  return (
-    <div className="flex items-center justify-center p-8 rounded-[var(--radius-lg)] border border-border bg-card text-card-foreground">
-      <p className="text-sm text-muted-foreground">
-        ✅ <strong>{label}</strong> — rendering normally. Click the button to simulate a crash.
-      </p>
-    </div>
-  );
-}
-
-// ── Wrapper that controls crash state ────────────────────────────────────────
-
-function CrashController({
-  Boundary,
-  label,
-}: {
-  Boundary: React.ComponentType<{ children: React.ReactNode }>;
-  label: string;
-}) {
-  const [crashed, setCrashed] = useState(false);
-
-  return (
-    <div className="space-y-4">
-      <button
-        onClick={() => setCrashed(true)}
-        disabled={crashed}
-        className="inline-flex items-center px-4 py-2 text-sm rounded-[var(--radius-button)] bg-destructive text-destructive-foreground hover:bg-destructive/90 disabled:opacity-40 disabled:cursor-not-allowed"
-      >
-        Simulate crash
-      </button>
-
-      <Boundary>
-        <Crashable shouldCrash={crashed} label={label} />
-      </Boundary>
-    </div>
-  );
-}
-
-// ── Meta ──────────────────────────────────────────────────────────────────────
-
-const meta: Meta = {
-  title: 'Shared/ErrorBoundary',
-  parameters: {
-    layout: 'padded',
-    docs: {
-      description: {
-        component:
-          'Three pre-configured ErrorBoundary variants for root, page, and section-level error isolation. Click "Simulate crash" to see each fallback UI.',
-      },
-    },
-  },
-};
-
-export default meta;
-
-// ── Stories ───────────────────────────────────────────────────────────────────
-
-export const App: StoryObj = {
-  name: 'AppErrorBoundary (root fallback)',
-  render: () => <CrashController Boundary={AppErrorBoundary} label="App-level component" />,
-  parameters: {
-    docs: {
-      description: {
-        story:
-          '`AppErrorBoundary` renders a full-screen fallback using only inline styles — no Tailwind dependency — so it works even if the design system itself fails to load.',
-      },
-    },
-  },
-};
-
-export const Page: StoryObj = {
-  name: 'PageErrorBoundary (route fallback)',
-  render: () => <CrashController Boundary={PageErrorBoundary} label="Page component" />,
-  parameters: {
-    docs: {
-      description: {
-        story:
-          '`PageErrorBoundary` shows a half-height Tailwind-styled fallback. The sidebar, header, and other chrome remain visible — only the page content area is replaced.',
-      },
-    },
-  },
-};
-
-export const Section: StoryObj = {
-  name: 'SectionErrorBoundary (inline fallback)',
-  render: () => (
-    <div className="space-y-6 max-w-2xl">
-      <p className="text-sm text-muted-foreground">
-        Each card below is independently wrapped. Crashing one does not affect the others.
-      </p>
-
-      {(['Team table', 'Chart', 'Assistant panel'] as const).map(label => (
-        <CrashController key={label} Boundary={SectionErrorBoundary} label={label} />
-      ))}
-    </div>
-  ),
-  parameters: {
-    docs: {
-      description: {
-        story:
-          '`SectionErrorBoundary` renders a compact inline fallback. Multiple independent sections on the same page can each fail in isolation.',
-      },
-    },
-  },
-};
+import type { Meta, StoryObj } from '@storybook/react';
+import React, { useState } from 'react';
+import { AppErrorBoundary, PageErrorBoundary, SectionErrorBoundary } from './error-boundary';
+
+// ── Crash helper ─────────────────────────────────────────────────────────────
+// A component that throws on the next render when `shouldCrash` is true.
+// Used in every story to demonstrate real boundary behaviour.
+
+function Crashable({ shouldCrash, label }: { shouldCrash: boolean; label: string }) {
+  if (shouldCrash) throw new Error(`Simulated crash in: ${label}`);
+  return (
+    <div className="flex items-center justify-center p-8 rounded-[var(--radius-lg)] border border-border bg-card text-card-foreground">
+      <p className="text-sm text-muted-foreground">
+        ✅ <strong>{label}</strong> — rendering normally. Click the button to simulate a crash.
+      </p>
+    </div>
+  );
+}
+
+// ── Wrapper that controls crash state ────────────────────────────────────────
+
+function CrashController({
+  Boundary,
+  label,
+}: {
+  Boundary: React.ComponentType<{ children: React.ReactNode }>;
+  label: string;
+}) {
+  const [crashed, setCrashed] = useState(false);
+
+  return (
+    <div className="space-y-4">
+      <button
+        onClick={() => setCrashed(true)}
+        disabled={crashed}
+        className="inline-flex items-center px-4 py-2 text-sm rounded-[var(--radius-button)] bg-destructive text-destructive-foreground hover:bg-destructive/90 disabled:opacity-40 disabled:cursor-not-allowed"
+      >
+        Simulate crash
+      </button>
+
+      <Boundary>
+        <Crashable shouldCrash={crashed} label={label} />
+      </Boundary>
+    </div>
+  );
+}
+
+// ── Meta ──────────────────────────────────────────────────────────────────────
+
+const meta: Meta = {
+  title: 'Shared/ErrorBoundary',
+  parameters: {
+    layout: 'padded',
+    docs: {
+      description: {
+        component:
+          'Three pre-configured ErrorBoundary variants for root, page, and section-level error isolation. Click "Simulate crash" to see each fallback UI.',
+      },
+    },
+  },
+};
+
+export default meta;
+
+// ── Stories ───────────────────────────────────────────────────────────────────
+
+export const App: StoryObj = {
+  name: 'AppErrorBoundary (root fallback)',
+  render: () => <CrashController Boundary={AppErrorBoundary} label="App-level component" />,
+  parameters: {
+    docs: {
+      description: {
+        story:
+          '`AppErrorBoundary` renders a full-screen fallback using only inline styles — no Tailwind dependency — so it works even if the design system itself fails to load.',
+      },
+    },
+  },
+};
+
+export const Page: StoryObj = {
+  name: 'PageErrorBoundary (route fallback)',
+  render: () => <CrashController Boundary={PageErrorBoundary} label="Page component" />,
+  parameters: {
+    docs: {
+      description: {
+        story:
+          '`PageErrorBoundary` shows a half-height Tailwind-styled fallback. The sidebar, header, and other chrome remain visible — only the page content area is replaced.',
+      },
+    },
+  },
+};
+
+export const Section: StoryObj = {
+  name: 'SectionErrorBoundary (inline fallback)',
+  render: () => (
+    <div className="space-y-6 max-w-2xl">
+      <p className="text-sm text-muted-foreground">
+        Each card below is independently wrapped. Crashing one does not affect the others.
+      </p>
+
+      {(['Team table', 'Chart', 'Assistant panel'] as const).map(label => (
+        <CrashController key={label} Boundary={SectionErrorBoundary} label={label} />
+      ))}
+    </div>
+  ),
+  parameters: {
+    docs: {
+      description: {
+        story:
+          '`SectionErrorBoundary` renders a compact inline fallback. Multiple independent sections on the same page can each fail in isolation.',
+      },
+    },
+  },
+};

package/components/shared/error-boundary.tsx

@@ -1,150 +1,150 @@
-import React from 'react';
-
-// ─────────────────────────────────────────────────────────────────────────────
-// ErrorBoundary — reusable class-based error boundary
-//
-// React error boundaries MUST be class components. This is the single base
-// implementation used throughout the app via three pre-configured wrappers:
-//
-//   <AppErrorBoundary>    — Root level: catches provider/context crashes
-//   <PageErrorBoundary>   — Route level: catches page-level render errors
-//   <SectionErrorBoundary>— Feature level: catches isolated section errors
-//
-// Usage:
-//   import { PageErrorBoundary } from '@/components/shared/error-boundary';
-//   <PageErrorBoundary><MyPage /></PageErrorBoundary>
-// ─────────────────────────────────────────────────────────────────────────────
-
-// ── Types ─────────────────────────────────────────────────────────────────────
-
-export interface FallbackProps {
-  error: Error;
-  reset: () => void;
-}
-
-interface ErrorBoundaryProps {
-  children: React.ReactNode;
-  /** Custom fallback UI. Receives the error and a reset callback. */
-  fallback: React.ComponentType<FallbackProps>;
-  /**
-   * Optional callback fired when an error is caught.
-   * Use to log to Sentry, Datadog, etc.
-   */
-  onError?: (error: Error, info: React.ErrorInfo) => void;
-  /**
-   * List of values that, when changed, automatically reset the boundary.
-   * Useful for resetting on route changes (pass `location.pathname`).
-   */
-  resetKeys?: unknown[];
-}
-
-interface ErrorBoundaryState {
-  hasError: boolean;
-  error: Error | null;
-}
-
-// ── Core class ────────────────────────────────────────────────────────────────
-
-export class ErrorBoundary extends React.Component<ErrorBoundaryProps, ErrorBoundaryState> {
-  constructor(props: ErrorBoundaryProps) {
-    super(props);
-    this.state = { hasError: false, error: null };
-    this.reset = this.reset.bind(this);
-  }
-
-  static getDerivedStateFromError(error: Error): ErrorBoundaryState {
-    return { hasError: true, error };
-  }
-
-  componentDidCatch(error: Error, info: React.ErrorInfo) {
-    this.props.onError?.(error, info);
-
-    if (import.meta.env.DEV) {
-      console.group('[ErrorBoundary] Uncaught error');
-      console.error(error);
-      console.error('Component stack:', info.componentStack);
-      console.groupEnd();
-    }
-  }
-
-  componentDidUpdate(prevProps: ErrorBoundaryProps) {
-    if (!this.state.hasError) return;
-
-    const { resetKeys } = this.props;
-    if (!resetKeys?.length) return;
-
-    const prevKeys = prevProps.resetKeys ?? [];
-    const changed = resetKeys.some((key, i) => key !== prevKeys[i]);
-    if (changed) this.reset();
-  }
-
-  reset() {
-    this.setState({ hasError: false, error: null });
-  }
-
-  render() {
-    const { hasError, error } = this.state;
-    const { children, fallback: Fallback } = this.props;
-
-    if (hasError && error) {
-      return <Fallback error={error} reset={this.reset} />;
-    }
-
-    return children;
-  }
-}
-
-// ── Pre-configured variants ───────────────────────────────────────────────────
-// Import the fallbacks from error-fallbacks.tsx to avoid circular deps.
-// These are thin wrappers so callers never need to wire up the fallback prop.
-
-import { AppErrorFallback, PageErrorFallback, SectionErrorFallback } from './error-fallbacks';
-
-interface BoundaryProps {
-  children: React.ReactNode;
-  onError?: (error: Error, info: React.ErrorInfo) => void;
-  resetKeys?: unknown[];
-}
-
-/**
- * `AppErrorBoundary` — root level.
- *
- * Place at the very top of the tree, outside all providers. If something inside
- * the provider stack crashes during setup, this boundary prevents a blank screen.
- */
-export function AppErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
-  return (
-    <ErrorBoundary fallback={AppErrorFallback} onError={onError} resetKeys={resetKeys}>
-      {children}
-    </ErrorBoundary>
-  );
-}
-
-/**
- * `PageErrorBoundary` — route level.
- *
- * Wrap `<AppRoutes>` / `<AuthGuard>` inside the router. When a lazy page chunk
- * fails to load, or a page component throws, the rest of the app (providers,
- * nav chrome) stays alive and only the page area shows the error UI.
- */
-export function PageErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
-  return (
-    <ErrorBoundary fallback={PageErrorFallback} onError={onError} resetKeys={resetKeys}>
-      {children}
-    </ErrorBoundary>
-  );
-}
-
-/**
- * `SectionErrorBoundary` — feature/section level.
- *
- * Use around individual sections within a page (e.g., a data table, a chart,
- * the assistant panel). An error in one section does not crash the entire page.
- */
-export function SectionErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
-  return (
-    <ErrorBoundary fallback={SectionErrorFallback} onError={onError} resetKeys={resetKeys}>
-      {children}
-    </ErrorBoundary>
-  );
-}
+import React from 'react';
+
+// ─────────────────────────────────────────────────────────────────────────────
+// ErrorBoundary — reusable class-based error boundary
+//
+// React error boundaries MUST be class components. This is the single base
+// implementation used throughout the app via three pre-configured wrappers:
+//
+//   <AppErrorBoundary>    — Root level: catches provider/context crashes
+//   <PageErrorBoundary>   — Route level: catches page-level render errors
+//   <SectionErrorBoundary>— Feature level: catches isolated section errors
+//
+// Usage:
+//   import { PageErrorBoundary } from '@/components/shared/error-boundary';
+//   <PageErrorBoundary><MyPage /></PageErrorBoundary>
+// ─────────────────────────────────────────────────────────────────────────────
+
+// ── Types ─────────────────────────────────────────────────────────────────────
+
+export interface FallbackProps {
+  error: Error;
+  reset: () => void;
+}
+
+interface ErrorBoundaryProps {
+  children: React.ReactNode;
+  /** Custom fallback UI. Receives the error and a reset callback. */
+  fallback: React.ComponentType<FallbackProps>;
+  /**
+   * Optional callback fired when an error is caught.
+   * Use to log to Sentry, Datadog, etc.
+   */
+  onError?: (error: Error, info: React.ErrorInfo) => void;
+  /**
+   * List of values that, when changed, automatically reset the boundary.
+   * Useful for resetting on route changes (pass `location.pathname`).
+   */
+  resetKeys?: unknown[];
+}
+
+interface ErrorBoundaryState {
+  hasError: boolean;
+  error: Error | null;
+}
+
+// ── Core class ────────────────────────────────────────────────────────────────
+
+export class ErrorBoundary extends React.Component<ErrorBoundaryProps, ErrorBoundaryState> {
+  constructor(props: ErrorBoundaryProps) {
+    super(props);
+    this.state = { hasError: false, error: null };
+    this.reset = this.reset.bind(this);
+  }
+
+  static getDerivedStateFromError(error: Error): ErrorBoundaryState {
+    return { hasError: true, error };
+  }
+
+  componentDidCatch(error: Error, info: React.ErrorInfo) {
+    this.props.onError?.(error, info);
+
+    if (import.meta.env.DEV) {
+      console.group('[ErrorBoundary] Uncaught error');
+      console.error(error);
+      console.error('Component stack:', info.componentStack);
+      console.groupEnd();
+    }
+  }
+
+  componentDidUpdate(prevProps: ErrorBoundaryProps) {
+    if (!this.state.hasError) return;
+
+    const { resetKeys } = this.props;
+    if (!resetKeys?.length) return;
+
+    const prevKeys = prevProps.resetKeys ?? [];
+    const changed = resetKeys.some((key, i) => key !== prevKeys[i]);
+    if (changed) this.reset();
+  }
+
+  reset() {
+    this.setState({ hasError: false, error: null });
+  }
+
+  render() {
+    const { hasError, error } = this.state;
+    const { children, fallback: Fallback } = this.props;
+
+    if (hasError && error) {
+      return <Fallback error={error} reset={this.reset} />;
+    }
+
+    return children;
+  }
+}
+
+// ── Pre-configured variants ───────────────────────────────────────────────────
+// Import the fallbacks from error-fallbacks.tsx to avoid circular deps.
+// These are thin wrappers so callers never need to wire up the fallback prop.
+
+import { AppErrorFallback, PageErrorFallback, SectionErrorFallback } from './error-fallbacks';
+
+interface BoundaryProps {
+  children: React.ReactNode;
+  onError?: (error: Error, info: React.ErrorInfo) => void;
+  resetKeys?: unknown[];
+}
+
+/**
+ * `AppErrorBoundary` — root level.
+ *
+ * Place at the very top of the tree, outside all providers. If something inside
+ * the provider stack crashes during setup, this boundary prevents a blank screen.
+ */
+export function AppErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
+  return (
+    <ErrorBoundary fallback={AppErrorFallback} onError={onError} resetKeys={resetKeys}>
+      {children}
+    </ErrorBoundary>
+  );
+}
+
+/**
+ * `PageErrorBoundary` — route level.
+ *
+ * Wrap `<AppRoutes>` / `<AuthGuard>` inside the router. When a lazy page chunk
+ * fails to load, or a page component throws, the rest of the app (providers,
+ * nav chrome) stays alive and only the page area shows the error UI.
+ */
+export function PageErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
+  return (
+    <ErrorBoundary fallback={PageErrorFallback} onError={onError} resetKeys={resetKeys}>
+      {children}
+    </ErrorBoundary>
+  );
+}
+
+/**
+ * `SectionErrorBoundary` — feature/section level.
+ *
+ * Use around individual sections within a page (e.g., a data table, a chart,
+ * the assistant panel). An error in one section does not crash the entire page.
+ */
+export function SectionErrorBoundary({ children, onError, resetKeys }: BoundaryProps) {
+  return (
+    <ErrorBoundary fallback={SectionErrorFallback} onError={onError} resetKeys={resetKeys}>
+      {children}
+    </ErrorBoundary>
+  );
+}