Fix issue loading tasks as starting page#2352
Conversation
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
📝 WalkthroughWalkthroughThis PR introduces a structured error boundary system across the viewer frontend. The error handler now accepts plain ChangesError Boundary System
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
UI unit Tests 1 files ± 0 3 suites - 59 0s ⏱️ -32s Results for commit 3bb0d26. ± Comparison against base commit 78e3f97. This pull request removes 186 and adds 10 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
so stack trace is shown and copy/pastable

On my phone the tasks page is cached as the starting page and there's a JS error because the project is not ready. This caused me to be stuck on the page. I fixed the root cause and provided a failsafe.
#2316 provided one failsafe. This PR provides another using a
svelte:boundaryto catch render errors and provide a way to try again or close the project or open the sidebar.Forcing an error to happen when rendering the tasks view looks like this:

it's a little weird to have the sidebar toggle twice, but it doesn't hurt. The new error handler is also used on the Browse View, but I didn't force an error to test that version.