fix: handle v-for + custom directive should trigger unmounted #12572
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.
close #12569
try to simulate this case using component
In this issue, if I use a component to simulate this case, vue can trigger the component's onUnmounted hook, because when collecting dynamicChildren, ShapeFlags.COMPONENT is always collected.
core/packages/runtime-core/src/vnode.ts
Line 524 in 833f9ea
So I think if vnode uses runtime dirctives, it should also be collected into dynamicChildren,Or mark this v-for fragment as not STABLE_FRAGMENT?