fix(gui): clear remaining react-doctor code findings#480
Conversation
|
Warning Review limit reached
Next review available in: 36 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe GUI now uses shared i18n modules, explicit dialog backdrop controls, semantic interactive markup, safer async cleanup and HTTP handling, immutable sorting, cached number formatting, provider workspace tiering, and stable identifiers for Claude model mappings. ChangesGUI cleanup and reliability
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Fix effect cleanup, mechanical a11y/perf warnings, barrel imports, button types, dialog roles, fetch status checks, loading finally resets, unused exports, and related GUI correctness issues. Doctor policy/config changes land in a separate PR.
c8d5df1 to
3089791
Compare
React-doctor cleanup removed isPaidProvider, pickCanonicalForwardProvider, providerBrandColor, and sortPresets. Sync provider-workspace-data tests so bun test no longer fails on missing named exports.
Restore insecure-context UUIDs, poll timeouts, modal stacking/a11y, notes save/focus, list semantics, and related GUI test expectations from PR lidge-jun#480 review threads.
CodeRabbit on lidge-jun#480: updateProvider now awaits fetchConfig before returning success, and ProviderOverview notes save has regression coverage for rejected and deferred successful updates.
|
Addressed the two CodeRabbit notes-save threads:
Pushed in a404a45. |
Summary
finallyresets, unused exports, toSorted/structuredClone, provider catalog polish, and related GUI issues.gui/doctor.config.json,gui/.react-doctor-ignores.md) moved to chore(gui): document intentional react-doctor policy disables #481 so this lands independently of intentional rule disables.Note on doctor score
Full
npx react-doctor@0.9.1 --scope full100/100 still needs #481 (rule disables for SPA fetch-in-effect, giant components / useReducer, parent sync effects, draft JSON editor derived state, etc.). This PR alone may leave policy-gated diagnostics.Test plan
bun run lint:guibun x tsc -p gui/tsconfig.app.json --noEmit(same 3 pre-existing errors currently ondev)Split
Companion policy/config: #481
Summary by CodeRabbit