fix(reticulum): CodeRabbit a11y and listener-off retry toast - #748
Conversation
Darken the Remote pending-offer badge, align 99+ aria with the visible cap, add axe coverage, and toast listener-off distinctly when retry skips the enable modal.
|
Warning Review limit reached
Next review available in: 5 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: QUIET Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (16)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe changes update RNCP message formatting, Remote transfer retry feedback, and Remote pending-offer badge styling and accessibility tests. ChangesRemote transfer updates
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Drop mesh-client UI paths and the request-enable sentinel from outbound LXMF so Sideband/Nomad peers get a clear human ask for their rncp receive hash.
Restore the trailing mesh-client sentinel so receivers still open the enable/share modal, while leaving the human LXMF line app-agnostic.
…miss Auto-dismiss repeat enable-requests when already listening, broaden identity resolve before Always allow, and soften the toast when Ask enables without an identity hash yet.
Summary
bg-amber-800), capped99+aria label, axe coverage for badge/banner.listenerLikelyOffwithout opening the enable-request modal.Test plan
99+when pending offers exceed 99.Summary by CodeRabbit
Bug Fixes
Accessibility