docs: fix README drift — broken DPoP link, stale What's New banner, stale migration notice#878
Conversation
|
Warning Review limit reached
Next review available in: 55 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 (2)
WalkthroughUpdates Documentation corrections
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
…ating note - Fix package name typo: flutter_auth0 → auth0_flutter in Credentials Manager custom implementation section - Remove duplicate partial TOC block (lines 59–82 re-listed Web Auth section headings that were already in the full TOC above) - Clarify My Account API setup note: the gating requirement is MRRT (Multi-Resource Refresh Tokens), not the My Account API itself — the old note incorrectly implied the API feature itself needed to be enabled by support, which is no longer accurate
d8cc32a to
f5a6a25
Compare
Summary
Documentation drift fixes for
auth0-flutterv2.3.0 — audited against the live API surface.README.md (3 fixes)
MIGRATION_GUIDE.md(P2)EXAMPLES.md (3 fixes)
flutter_auth0→auth0_flutterin Credentials Manager section (P3)Test plan
## What's New: v2.3.0banner accurately describes passkeys and links to the passkeys docsauth0_flutterpackage name is used consistently throughout EXAMPLES.md🤖 Generated with syncing-sdk-docs skill
Summary by CodeRabbit
New Features
Documentation