Key generation

Nobody has claimed this yet.

The way the key for each item is being generated is not ideal as it uses the index of the item.

If you remove an item from the list, all the item DOM elements below that item in the list are removed and re-inserted as their index changes by -1 (not just re-rendered and compared against the virtual dom, they are actually removed and re-added (because of the key) which is a costly operation when you have a lot of elements).

The same is true if you re-order the source list, the component should be able to keep track of the objects between renders, regardless if one is removed or reordered in the source list.

Start at the component's list-rendering and key-generation logic described in the issue. Check how removing and reordering source items affects existing DOM elements; done means items retain stable identity without unnecessary removal and reinsertion.

Written by the indexing model from the issue text.