-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
refactor(router-core): trimPathRight more performant w/o trailing slash #5909
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
refactor(router-core): trimPathRight more performant w/o trailing slash #5909
Conversation
WalkthroughUpdated Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (4)📓 Common learnings📚 Learning: 2025-10-01T18:30:26.591ZApplied to files:
📚 Learning: 2025-09-22T00:56:49.237ZApplied to files:
📚 Learning: 2025-09-22T00:56:53.426ZApplied to files:
🧬 Code graph analysis (1)packages/router-core/src/path.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 (1)
Comment |
|
View your CI Pipeline Execution ↗ for commit 88f3ed7
☁️ Nx Cloud last updated this comment at |
trimPathRightis used on everymatchRoutescall, any perf is good to takebench
TL;DR: same when there is a trailing slash, 2x faster when there isn't.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.