Add residential field to Anonymizer response#664
Conversation
The minFraud Insights and Factors responses now include a residential object inside the ip_address anonymizer object. This is surfaced via the AnonymizerFeed record on the geoip2 Anonymizer record, which IpAddress reuses, so no model changes are needed here. Update the test fixtures and assertions to cover the new field and document the required geoip2 dependency bump in the changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 59 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 support for the new residential field in the Anonymizer response record, sourced from the GeoIP Residential Proxy feed. The changes include updating the CHANGELOG, adding test assertions in InsightsResponseTest.java, and updating the mock JSON response files (factors-response.json and insights-response.json) to include the new residential object. There are no review comments, and I have no additional 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.
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-java#740. At release time the
geoip2dependency in pom.xml must be bumped to 5.2.0 once released; CI will be red until then since the fixtures exercise the new field.Testing
With geoip2 built from that PR (mvn install to the local repo; pom.xml unchanged): mvn -B test 237 tests pass; checkstyle clean.
🤖 Generated with Claude Code