fix(referral/verify): stop exposing inviter's internal user id in response - #1467
fix(referral/verify): stop exposing inviter's internal user id in response#1467rajanpanth wants to merge 1 commit into
Conversation
…ponse The public, unauthenticated referral-verify endpoint returned the inviter's internal user id in the response alongside their display name and photo. The id isn't used by the invite UI and only aids enumeration. It's removed from the response payload; it remains selected internally because the remaining-slots count keys on it.
|
@rajanpanth is attempting to deploy a commit to the Superteam Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
Next review available in: 58 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
The public, unauthenticated
referral/verifyendpoint returned the inviter's internal useridin the response alongside their display name and photo. Theidisn't used by the invite UI and only aids enumeration, so it's removed from the response payload.It remains in the Prisma
selectbecause the remaining-slots count keys on it. Display name and photo (needed to render the invite screen) are unchanged.pnpm check-typesandpnpm lintpass.