-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
feat(vue-app): function watchQuery #6297
Conversation
I fear the watchQuery function indeed very much 😆 |
? |
See the PR title |
Codecov Report
@@ Coverage Diff @@
## dev #6297 +/- ##
=====================================
Coverage 95.7% 95.7%
=====================================
Files 79 79
Lines 2652 2652
Branches 683 683
=====================================
Hits 2538 2538
Misses 98 98
Partials 16 16
Continue to review full report at Codecov.
|
Opps😱 |
packages/vue-app/template/client.js
Outdated
@@ -279,6 +279,7 @@ async function render(to, from, next) { | |||
// Get route's matched components | |||
const matches = [] | |||
const Components = getMatchedComponents(to, matches) | |||
const instances = getMatchedComponentsInstances(to) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be moved to the watchQuery else if
(eg using memoization)?
The need for instances
is for such a specific use-case only that we shouldnt always spent those cpu cycles retrieving them when there is a reasonable chance we dont need them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Types of changes
Description
Be merged after 2.9.2
Checklist: