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
Variables defined with let
behave differently (v3.2.45)
#7417
Comments
When the component re-renders because you changed the ref, the whole template is updated with all of the latest data. That's how re-renders work. the whole component template virtualDOM is re-rendered with the current data and diffed against the previous version. |
@LinusBorg |
It isn't - you an see for yourself in the playground, you can switch versions there. If you have a repository to share where this happens, please share it. |
I have prepared a repository to reproduce this issue. We would appreciate it if you could check it here. |
Vue version
3.2.45
Link to minimal reproduction
sfc link
Steps to reproduce
Start vue (up to 3.2.44) with yarn dev and access it with a browser using the following sample code.
What is expected?
What is actually happening?
When the previous code is executed in vue 3.2.45, the behavior of timeStr and timeStr(ref) is the same.
System Info
Any additional comments?
Is there a mistake in the way it is written? If so, I would like to know if you can help me.
note
I can only reproduce this event with Vue SFC PlayGround with the same behavior as 3.2.45. You can actually use the terminal to specify 3.2.44 or 3.2.45 in package.json and run rm yarn.lock && yarn install && yarn dev, etc. to confirm.
The text was updated successfully, but these errors were encountered: