-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Description
Version
4.0.11
Reproduction link
Steps to reproduce
- Click
Home
andAbout
a few times. - Check the console, and note that the computed is re-triggering on each navigation.
What is expected?
A method like Router#resolve
should not have "side-effects". It's not usable inside computed/composition functions, as it causes a re-run.
What is actually happening?
It's causing a re-trigger of the computed method.
I could be wrong, but I think it's because resolve
is reading from currentRoute
, and currentRoute
is being written to during navigation.
Would it be possible to read the values from currentRoute
without triggering dependencies?
Metadata
Metadata
Assignees
Labels
No labels