Add residential proxy data to anonymizer object#1915
Conversation
This surfaces the new residential sub-object nested within the anonymizer object in the minFraud Insights and Factors ip_address response. The IpAddress model reuses GeoIP2-node's AnonymizerRecord type directly and the response parsing recursively camelCases nested objects, so the new field flows through automatically once the @maxmind/geoip2-node dependency is updated to a version that types it. This commit updates the fixture and test coverage and documents the change, along with the future dependency bump, in the changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
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 (3)
✨ 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 anonymizer object on IpAddress, sourced from the GeoIP Residential Proxy database. The changes include updating the CHANGELOG, adding mock data to fixtures/insights.json, and updating the unit tests in src/response/models/insights.spec.ts to assert the new property. There are no review comments, so no feedback is provided.
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.
1 participant
Summary
Surfaces the new
residentialsub-object of theanonymizerobject in the minFraud Insights and Factorsip_addressresponse. The models reuse the GeoIP2 library's Anonymizer record, so this is a fixtures/tests/changelog change; the field flows through via the dependency.Depends on maxmind/GeoIP2-node#1738. At release time the
@maxmind/geoip2-nodedependency should be bumped to^7.1.0once published (the data flows through at runtime even on 7.0.0 since parsing is generic, but the types require 7.1.0).Testing
npm test 218/218 and npm run lint clean against published 7.0.0; re-verified against the PR branch via a temporary file: dependency (not committed).
🤖 Generated with Claude Code