Repository navigation
inherit cognitive nesting without penalizing parent functions (#165) - #167
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (22)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughNested functions no longer add cognitive-complexity points to enclosing scopes. Nested functions, class field initializers, and static blocks are scored separately, with nesting inherited from the enclosing scope. Tests and fixture annotations cover the updated scores. ChangesCognitive complexity scoring
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to This change stops nested functions from adding complexity points to their parent functions, and nested units now inherit nesting from the enclosing scope. Scores for functions with nested callbacks will change, but that is the documented intent and the tests and fixtures were updated to match. No merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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. I’m a rabbit counting branches in the glade, Comment |
Summary by CodeRabbit