Skip to content

fix(runtime-core): named ref, Non-ref data should not be contaminated #7522

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

liuxiaojun666
Copy link

@liuxiaojun666 liuxiaojun666 commented Jan 13, 2023

@liuxiaojun666 liuxiaojun666 changed the title Fix/runtime core renderer template named red Fix/named ref, Non-ref data should not be contaminated Jan 13, 2023
@liuxiaojun666 liuxiaojun666 changed the title Fix/named ref, Non-ref data should not be contaminated fix(runtime-core): named ref, Non-ref data should not be contaminated Jan 13, 2023
@LinusBorg LinusBorg linked an issue Jan 13, 2023 that may be closed by this pull request
@netlify
Copy link

netlify bot commented Jan 13, 2023

Deploy Preview for vuejs-coverage failed.

Name Link
🔨 Latest commit e0a4660
🔍 Latest deploy log https://app.netlify.com/sites/vuejs-coverage/deploys/63c14d4fffb8fd00088708e6

@liuxiaojun666
Copy link
Author

Workflow failed unexpectedly, please try again. @LinusBorg

@edison1105
Copy link
Member

This usage does not work in the production build, and there is a warning if you use a non-ref value hold element(via #12051). So, maybe this PR is no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Review
Development

Successfully merging this pull request may close these issues.

TemplateRef overwrites reactive data
3 participants