fix: merge account extra settings at the subkey level - #66
Conversation
The account settings PUT is full-replace with no server-side nil-check on the nested `extra` object, so a task naming only one extra_* option (e.g. extra_network_traffic_logs_enabled) silently reset every other extra setting (peer_approval_enabled, user_approval_required, etc.) to its zero value. Merge `extra` against the current settings at the subkey level instead of splicing the whole nested object in wholesale, mirroring the fallback pattern already used in netbird_group. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthrough
ChangesAccount settings merge
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change is localized to account settings merging and no actionable merge-blocking risk remains beyond normal checks and review. Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
The account settings PUT is full-replace with no server-side nil-check on the nested
extraobject, so a task naming only one extra_* option (e.g. extra_network_traffic_logs_enabled) silently reset every other extra setting (peer_approval_enabled, user_approval_required, etc.) to its zero value. Mergeextraagainst the current settings at the subkey level instead of splicing the whole nested object in wholesale, mirroring the fallback pattern already used in netbird_group.Summary by CodeRabbit
Bug Fixes
Tests