-
Notifications
You must be signed in to change notification settings - Fork 392
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(engine): fixes #663 - unique keys for slotted elements #664
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -573,7 +573,12 @@ export function allocateInSlot(vm: VM, children: VNodes) { | |
const data = (vnode.data as VNodeData); | ||
const slotName = ((data.attrs && data.attrs.slot) || '') as string; | ||
const vnodes: VNodes = cmpSlots[slotName] = cmpSlots[slotName] || []; | ||
vnodes.push(vnode); | ||
// re-keying the vnodes is necessary to avoid conflicts with default content for the slot | ||
// which might have similar keys. Each vnode will always have a key that | ||
// starts with a numeric character from compiler. In this case, we add a unique | ||
// notation for slotted vnodes keys, e.g.: `@foo:1:1` | ||
vnode.key = `@${slotName}:${vnode.key}`; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is the re-keying routine, only for fallback mode. |
||
ArrayPush.call(vnodes, vnode); | ||
} | ||
if (!vm.isDirty) { | ||
// We need to determine if the old allocation is really different from the new one | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we were using dot notation here :(