OpenCut-app / OpenCut-app/OpenCut
[UX] Add error boundaries around editor panels to prevent full-page crashes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Description
No React error boundaries exist in the editor. If any panel (preview, timeline, properties) throws a render error, the entire editor crashes to a blank screen.
Expected Behavior
Wrap critical editor panels with error boundaries that show a friendly fallback UI with:
- Error message
- "Retry" button
- Option to report the error
Priority Panels
- Preview canvas (
PreviewCanvas) - Timeline panel
- Effects/properties panel
Files
apps/web/src/app/error.tsx(doesn't exist — should be created)apps/web/src/components/editor/panels/preview/index.tsxapps/web/src/components/editor/panels/timeline/index.tsx
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the requested entry point in apps/web/src/app/error.tsx and the existing panel components at apps/web/src/components/editor/panels/preview/index.tsx and timeline/index.tsx. Trace how the preview, timeline, and effects/properties panels are rendered, then verify that a panel error shows the specified fallback with an error message, Retry button, and report option without blanking the full editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100