chore: Fail fast for migration DTO null contracts#1571
Conversation
Align migration DTO null handling with the existing Debug.Assert contracts so invalid internal calls fail fast instead of being silently normalized. Pin the contract behavior for rule data results and migration file path snapshots.
|
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 (4)
📝 WalkthroughWalkthroughConstructors and copy logic in third-party tool migration domain classes now throw ArgumentNullException for null arguments (filePaths, originalParameters, removedParameters, content, removedPlayerLoopTimingSignatures) instead of substituting empty defaults. Corresponding unit tests were added to verify this fail-fast behavior. ChangesFail-fast validation for migration domain objects
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 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. Comment |
Summary
User Impact
Changes
Verification