invoke-ai/InvokeAI

[enhancement]: Better Error Boundaries

Open

#4,498 建立於 2023年9月9日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)TypeScript (20,358 star) (2,164 fork)batch import
enhancementgood first issueweb ui

描述

Is there an existing issue for this?

  • I have searched the existing issues

Contact Details

No response

What should this feature add?

Currently we have one "global" error boundary, catching exceptions that bubble up to the root of the application.

We should implement much more granular error boundaries across the application.

This could be implemented in parts:

  • enhance the error boundary fallback component to be more descriptive and useful
    • scrollable area to display the full error?
    • probably should have a "refresh" button in addition to "reset", as often all that's needed is to refresh the page
    • make it configurable using AppConfig / configSlice so that eg commercial can provide their own components or URLs
  • utilize it in other areas - like one for canvas, one for nodes, one for gallery, etc

Alternatives

No response

Additional Content

No response

貢獻者指南

技術棧
typescriptreactcss
領域
frontend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
React error boundariesTypeScriptInvokeAI codebase structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Start by examining the current global error boundary in the codebase (likely in src/). Identify the fallback component and how it's used. Look at AppConfig and configSlice to understand how to make the fallback configurable. Then propose implementing granular error boundaries for canvas, nodes, gallery etc. Check if there are any existing discussions or PRs (none found). Consider adding a refresh button and scrollable error display.