perf(transform-vif): don't need to createBlock for a component #853
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
For |
|
@yyx990803 I still have some confusion, because a component will always add into parent's dynamic children list when create vnode |
|
Yes you're right. |
yyx990803
reviewed
Mar 20, 2020
| @@ -212,7 +212,10 @@ function createChildrenCodegenNode( | |||
| const vnodeCall = (firstChild as ElementNode) | |||
| .codegenNode as BlockCodegenNode | |||
| // Change createVNode to createBlock. | |||
| if (vnodeCall.type === NodeTypes.VNODE_CALL) { | |||
| if ( | |||
| vnodeCall.type === NodeTypes.VNODE_CALL && | |||
There was a problem hiding this comment.
Let's add a comment here: "component vnodes are always tracked and its children are compiled into slots so no need to make it a block"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.