docs(client): point builder reliability opt-out at ReliabilityConfig::disabled() (LAB-1059) - #57
Conversation
…:disabled() (LAB-1059) The CacheKitBuilder::reliability rustdoc was the one opt-out surface #50 missed - it still taught the all-None config prose that ReliabilityConfig::disabled() replaced in README, preset docs, and the reliability rustdoc. Same panel MIN, same fix, last surface.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 49 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 Run ID: 📒 Files selected for processing (1)
Comment |
Kody Review CompleteGreat news! 🎉 Keep up the excellent work! 🚀 Kody Guide: Usage and ConfigurationInteracting with Kody
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
Follow-up to #50 (LAB-729 panel MIN, tracked by LAB-1059): the
CacheKitBuilder::reliabilitymethod rustdoc was the one opt-out surface #50 missed — it still taught the old "pass a config with all layersNone" prose. Point it atReliabilityConfig::disabled()like the README, preset docs (intents.rs), and reliability rustdoc already do.Docs-only, 3-line rustdoc prose change.
cargo doc --features reliabilityclean for this link (the two pre-existingInteropValue/deserializeunresolved-link warnings in interop docs are untouched); doc-tests green.