Fix issue with routing performance when using updateOnRouterChange #98
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.
Fix for #97
Summary of changes:
Intended/example use case:
When using
updateOnRouterChange
the update would fire multiple times per route change causing performance problems. With this change the update will fire only once after a successful navigation.Checklist:
npm run build
runs without errorng serve
spawns app, Intercom messenger is visible and interactive, and there are no errors in the consoleCloses issue: #