-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
refactor(router-core): improve server store performance by removing getter/setter #6502
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
📝 WalkthroughWalkthroughInternal refactoring of the server store implementation in router-core, switching from a closure-based state management pattern to a direct object-based approach. The public API surface remains unchanged while the internal state mechanism transitions from an enclosed variable with getter/setter methods to a mutable store object with a state property. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Comment |
|
View your CI Pipeline Execution ↗ for commit 7946fb6
☁️ Nx Cloud last updated this comment at |
Compared to direct property access, getters / setters have a non-negligible performance cost. In the case of
createServerStorewe can significantly improve the performance of the store by using direct property access to the state.before
after
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.