refactor: remove default_peers_for_network from ClientConfig#592
Conversation
The function returned empty peers for mainnet/testnet (already the `Default` behavior) and a hardcoded `127.0.0.1:19899` for regtest that no caller actually relied on — dashd tests always clear and add their own peer.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe changes remove automatic network-specific peer initialization from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v0.42-dev #592 +/- ##
=============================================
- Coverage 67.40% 67.01% -0.40%
=============================================
Files 318 318
Lines 67020 67015 -5
=============================================
- Hits 45175 44909 -266
- Misses 21845 22106 +261
|
The function returned empty peers for mainnet/testnet (already the
Defaultbehavior) and a hardcoded127.0.0.1:19899for regtest that no caller actually relied on — dashd tests always clear and add their own peer.Summary by CodeRabbit