<p dir="auto">Thank you so much for this awesome framework. I've only been working with the framework for a couple of months now, and still unsure of all of the limitations. This looks like a limitation of the component system.</p>
<h3 dir="auto">Vue.js version</h3>
<p dir="auto">1.0.26</p>
<h3 dir="auto">Reproduction Link</h3>
<p dir="auto"><a href="https://jsfiddle.net/CristianGiordano/cdLp4uz2/" rel="nofollow">https://jsfiddle.net/CristianGiordano/cdLp4uz2/</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">Move a person from one list to another (The list component is re-rendered alongside the moved dom node)</p>
<h3 dir="auto">What is Expected?</h3>
<p dir="auto">No duplication of elements. Here is a working version (same code) without a <code class="notranslate">person</code> component.</p>
<p dir="auto"><a href="https://jsfiddle.net/CristianGiordano/ghwgzgtx/" rel="nofollow">https://jsfiddle.net/CristianGiordano/ghwgzgtx/</a></p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">It looks like VueJS cannot re-use existing nodes or find the node which was moved.</p>
<ul dir="auto">
<li>I have tried adding a <code class="notranslate">track-by</code> id with the relevant object properties.</li>
<li>I have tried SortableJS and Dragula sorting libraries with the same issue.</li>
</ul>
<p dir="auto">p.s. Apologies if this is not the right forum to raise such an issue.</p>
<h3 dir="auto">What problem does this feature solve?</h3>
<p dir="auto">If a user needs to implement a lifecycle hook that depends on async operations, vue should respect the async nature of the implemented hook and await it in vue land.</p>
<h3 dir="auto">What does the proposed API look like?</h3>
<p dir="auto">The API does not change; only how it works now by awaiting async hooks.</p>