Skip to content

fix: unify answer recovery states#760

Closed
BigSimmo wants to merge 2 commits into
mainfrom
codex/clinical-journey-recovery-pr
Closed

fix: unify answer recovery states#760
BigSimmo wants to merge 2 commits into
mainfrom
codex/clinical-journey-recovery-pr

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary: Unifies answer journey recovery states into shared EmptyState behavior for consistent no-results/cancel/failure handling in ClinicalDashboard. Changes: ClinicalDashboard.tsx, ui-primitives.tsx, tests/ui-primitives.dom.test.tsx. Scope is PR-safe and isolated via cherry-pick onto origin/main.

@supabase

supabase Bot commented Jul 17, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a363b6e1-7452-434b-9a3c-829b522e4e2b

📥 Commits

Reviewing files that changed from the base of the PR and between fb35cab and a9d5c7c.

📒 Files selected for processing (3)
  • src/components/ClinicalDashboard.tsx
  • src/components/ui-primitives.tsx
  • tests/ui-primitives.dom.test.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/clinical-journey-recovery-pr

Comment @coderabbitai help to get the list of available commands.

@BigSimmo
BigSimmo enabled auto-merge July 17, 2026 20:03
@BigSimmo BigSimmo mentioned this pull request Jul 17, 2026
8 tasks
@BigSimmo BigSimmo closed this Jul 17, 2026
auto-merge was automatically disabled July 17, 2026 20:14

Pull request was closed

@BigSimmo
BigSimmo deleted the codex/clinical-journey-recovery-pr branch July 18, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant