Skip to content
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

fix(stubs): Do not create stubs across multiple renders, fix #810 #813

Merged
merged 1 commit into from
Aug 5, 2021

Conversation

xanf
Copy link
Collaborator

@xanf xanf commented Jul 31, 2021

Fixes #810

Basically we need to cache our stubs so we do not create new stubs each render.
We already had this thing in place long ago for our automatic stubs (created either by shallow or with stub value set to true)

This PR uses same logic and unifies "storage" of created stubs

@xanf xanf force-pushed the xanf-fix-rerenders branch 2 times, most recently from f97867b to c9e7e4e Compare July 31, 2021 13:50
Copy link
Member

@lmiller1990 lmiller1990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nicely done. The stub madness begins again - so far this is much cleaner than V1, let's try to keep it that way. Thanks for this!

@lmiller1990 lmiller1990 merged commit 97926a2 into vuejs:master Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to reassign stubbed component with findComponent after update to 2.0.0-rc.10
2 participants