Complete HTTP task API and local task UI - #16
Conversation
|
Warning Review limit reached
Next review available in: 39 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR replaces the health-only web shell with a task-management UI, adding validated task API access, task views, capture/edit/lifecycle workflows, conflict reconciliation, tests, styling, coverage configuration, and refined HTTP error logging. ChangesTask management UI
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/src/App.tsx`:
- Around line 128-141: Update the header retry button in the health-status
rendering of App to use a distinct accessible name, such as “Retry connection,”
while keeping its checkHealth behavior unchanged. Ensure ErrorBanner’s reload
button retains the “Retry” name so task-list retry queries target the intended
button.
In `@web/src/hooks/useTaskView.ts`:
- Around line 15-18: Update the view-change branch in useTaskView to stop
clearing tasks when displayedView.current differs from view, so the previous
task list remains visible while the new view loads. Remove displayedView and its
related logic if it is no longer used after this change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 042f8343-1192-4855-9e76-612f39a17077
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (20)
docs/superpowers/plans/2026-07-25-local-task-management-ui.mdpackage.jsonsrc/interfaces/http/http-router.tstests/integration/http-tasks.test.tstests/unit/web/task-client.test.tsvitest.config.tsweb/src/App.test.tsxweb/src/App.tsxweb/src/api/task-client.tsweb/src/api/task-contracts.tsweb/src/components/ErrorBanner.tsxweb/src/components/TaskComposer.tsxweb/src/components/TaskDetailsPanel.tsxweb/src/components/TaskList.tsxweb/src/components/TaskRow.tsxweb/src/components/TaskStatusBadge.tsxweb/src/components/ViewNavigation.tsxweb/src/hooks/useTaskView.tsweb/src/main.tsxweb/src/styles.css
| if (displayedView.current !== view) { | ||
| displayedView.current = view; | ||
| setTasks([]); | ||
| } |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Retain the prior list while the new view loads.
Clearing tasks here causes a blank-state flicker on every view change, contrary to the plan’s requirement to retain displayed tasks while reloading. Remove this reset (and displayedView if it becomes unused).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@web/src/hooks/useTaskView.ts` around lines 15 - 18, Update the view-change
branch in useTaskView to stop clearing tasks when displayedView.current differs
from view, so the previous task list remains visible while the new view loads.
Remove displayedView and its related logic if it is no longer used after this
change.
1 participant
Completes the local task-management UI and finalizes the HTTP task API work. Includes task views, task lifecycle controls, metadata editing, API client coverage, and a correction so known persistence failures are not logged as unhandled HTTP failures.\n\nValidated with formatting, typechecking, linting, focused UI/API tests, and HTTP task integration tests.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation