fix(router-plugin): avoid redundant NGXS state updates for identical router snapshots #2372
+39
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the router plugin always patched NGXS state on every router event, even if the new router snapshot was identical to the current one. This caused unnecessary updates to the internal NGXS state signal, triggering recomputations of
selectSignalselectors and extra Angular change detection cycles.With this change, we now compare the current and incoming router state (trigger, navigationId, and serialized snapshot). If they are equal, the state update is skipped. This avoids redundant signal emissions, leading to fewer recomputations and improved performance in large apps.