[APIP] Populate TokenId from BasicAuth#207
Conversation
|
Warning Review limit reached
More reviews will be available in 49 minutes and 38 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Basic Auth policy handler now sets Suggested Reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@policies/basic-auth/go.mod`:
- Line 5: The v0.2.14 upgrade of github.com/wso2/api-platform/sdk/core
introduces breaking changes including new `ProcessingMode` requirements and
interface refactoring. While the basic-auth policy appears correctly updated
with the Mode() method and TokenId usage, verify that all related policies in
this cohort (jwt-auth, api-key-auth, and any others using the core SDK) have
identical updates to their interface implementations. Ensure each policy
implements the Mode() method, uses TokenId correctly, follows the new interface
structure, and uses the standardized import paths consistent with v0.2.14,
matching the pattern already established in the basic-auth policy
implementation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 2f9ae755-4c40-4282-ae6e-c6557ce49ff5
⛔ Files ignored due to path filters (1)
policies/basic-auth/go.sumis excluded by!**/*.sum
📒 Files selected for processing (2)
policies/basic-auth/basicauth.gopolicies/basic-auth/go.mod
Related to wso2/api-platform#2131
We use the given username as the tokenId