Add residential proxy data to anonymizer object#1738
Conversation
|
Warning Review limit reached
Next review available in: 58 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new residential property to the AnonymizerRecord interface within the GeoIP2 Insights response model. It defines a new AnonymizerFeedRecord interface containing confidence, networkLastSeen, and providerName fields, updates the test fixtures, and adds corresponding unit tests to verify the new property. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
oschwald
force-pushed
the
greg/stf-997-add-residential-to-anonymizer
branch
from
3595aa0 to
c27faa1
Compare
This adds support for the new residential sub-object nested within the anonymizer object in the GeoIP2 Insights web service response. The residential object contains a confidence score, the last seen date for the network, and the associated provider name. The residential property may be populated even when no other anonymizer properties are set. The shared shape of these feed records is exposed as a new AnonymizerFeedRecord interface so it can be reused if additional feeds are added in the future. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
oschwald
force-pushed
the
greg/stf-997-add-residential-to-anonymizer
branch
from
c27faa1 to
a08f851
Compare
1 participant
Summary
The GeoIP Insights web service is adding a
residentialsub-object to theanonymizerobject. It contains residential proxy data for the network and may be populated even when no other anonymizer properties are set.confidence,network_last_seen,provider_name) namedAnonymizerFeed, so future anonymizer feeds can share itresidentialproperty on theAnonymizerrecord(The reusable interface is named
AnonymizerFeedRecordper this repo's record-interface naming convention.)Testing
npm test,npm run lint,npm run build, andnpm run prettier:ciall pass.🤖 Generated with Claude Code