studio-error-handling

作者: supabase

Supabase Studio 的錯誤顯示與疑難排解模式。用於

npx skills add https://github.com/supabase/supabase --skill studio-error-handling

Studio Error Handling Pattern

Full docs and code examples: apps/studio/components/interfaces/ErrorHandling/README.md

How it works

Classification happens in the data layer: handleError in data/fetchers.ts tests the error message against ERROR_PATTERNS and throws the matching error subclass (e.g. ConnectionTimeoutError extends ResponseError). The component (ErrorMatcher) reads errorType from the instance and does an O(1) lookup — it never does regex matching.

handleError() → throws ConnectionTimeoutError → React Query catches → ErrorMatcher reads errorType → renders troubleshooting

Key files

FilePurpose
data/error-patterns.tsArray of { pattern, ErrorClass } — the regex lives here
types/api-errors.tsError classes, KnownErrorType union, ClassifiedError type
ErrorMatcher.tsxComponent — reads errorType, looks up mapping, renders
error-mappings.tsxRecord<KnownErrorType, { id, Troubleshooting: ComponentType }>
errorMappings/ConnectionTimeout.tsxReference troubleshooting component
TroubleshootingSections.tsxReusable accordion section components
TroubleshootingAccordion.tsxAccordion wrapper with telemetry

Usage

Pass the full error object from React Query — not error.message:

{
  isError && (
    <ErrorMatcher title="Failed to load tables" error={error} supportFormParams={{ projectRef }} />
  )
}

What NOT to do

  • Do not pass error.message to ErrorMatcher — pass the full error object so the class is preserved.
  • Do not put regex patterns in error-mappings.tsx — they belong in data/error-patterns.ts.
  • Do not use Object.assign to stamp errorType — throw a proper subclass instead.
  • Do not pass a raw URL string for support — use supportFormParams={{ projectRef }}.
  • Do not put the page title inside the error mapping — it belongs on the <ErrorMatcher> caller.
  • Do not add callback props (onDebugWithAI, onRestartProject) to troubleshooting components — use hooks inside them instead.

來自 supabase 的更多技能

studio-e2e-tests
supabase
撰寫並執行 Supabase Studio 的 Playwright E2E 測試。在收到要求時使用。
official
vitest
supabase
由 Vite 驅動、相容 Jest API 的 Vitest 快速單元測試框架。適用於撰寫測試、模擬、配置覆蓋率或處理測試相關工作時使用。
official
skill-creator
supabase
建立模組化技能的全面指南,可擴展 Claude 的功能,包含專業知識與工作流程。技能由必要的 SKILL.md 檔案(含 YAML 前置資料與 Markdown 指令)以及可選的捆綁資源(腳本、參考資料、素材)組成,這些資源按用途組織並逐步載入以節省上下文空間。圍繞具體使用範例設計技能;識別用於確定性任務的可重複使用腳本、用於領域知識的參考檔案,以及用於...的素材。
official
supabase
supabase
在執行任何涉及 Supabase 的任務時使用。觸發條件:Supabase 產品(資料庫、驗證、邊緣函數、即時功能、儲存、向量、排程、佇列);客戶端…
official
supabase-server
supabase
在撰寫 Supabase 伺服端程式碼時使用 — 包括 Edge Functions、Hono 應用程式、Webhook 處理器,或任何需要建立 Supabase 驗證與客戶端的後端環境。…
official
clickhouse-logs-queries
supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed `logs` table (the `logs.all.otel` analytics endpoint). Use this whenever a task…
official
dev-toolbar-review
supabase
在審查涉及 packages/dev-tools/、packages/common/posthog-client.ts 的 PR 時使用
official
e2e-studio-tests
supabase
在 Studio 應用程式中執行端對端測試。當被要求執行端對端測試、執行 Studio 測試、Playwright 測試或測試功能時使用。
official