-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(router-core): replaceEqualDeep max depth #6378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
📝 WalkthroughWalkthroughAdded internal depth-tracking parameter to Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (2)**/*.{ts,tsx}📄 CodeRabbit inference engine (AGENTS.md)
Files:
**/*.{js,ts,tsx}📄 CodeRabbit inference engine (AGENTS.md)
Files:
🧠 Learnings (2)📓 Common learnings📚 Learning: 2025-08-30T09:12:13.852ZApplied to files:
🧬 Code graph analysis (1)packages/router-core/src/utils.ts (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (2)
Comment |
|
View your CI Pipeline Execution ↗ for commit e19cdec
☁️ Nx Cloud last updated this comment at |
Add max depth for recursive
replaceEqualDeepto avoid insanely deep objects (500 nested levels) slowing/freezing the main thread. Beyond 500, we just return the new object.The function is still callable w/ the same parameters as before. It should have now impact on users, except for those that have insanely deep objects.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.