invoke-ai/InvokeAI

[enhancement]: Better Error Boundaries

Open

#4.498 geöffnet am 9. Sept. 2023

Auf GitHub ansehen
 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (2.164 Forks)batch import
enhancementgood first issueweb ui

Repository-Metriken

Stars
 (20.358 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 39T 7h) (39 gemergte PRs in 30 T)

Beschreibung

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

Contributor Guide