Keyed Nodes about morphdom HOT 5 CLOSED

Hi @kesne, morphdom uses the "id" attribute as the "key" by design. That is, morphdom works best if there are stable IDs for HTML elements and it will take extra steps to match up elements with matching IDs that are found in both the old DOM and the new DOM. Is there something else that you think is still missing?

from morphdom.

Ah, probably would have been good to read through the source before making an issue! My mistake.

I guess the only callout is that the benefit of a key design is that keys can be re-used in two different trees that you're running through morphdom, whereas IDs need to be absolutely unique.

from morphdom.

True. With Marko Widgets we have a strategy for ensure IDs are always unique by prefixing IDs with the ID of the parent widget. That trick has worked really well for Marko Widgets. For rendering lists of items we recommend using the index of the current iteration prefixed with the ID of the parent widget as the unique ID. If you have any other thoughts or suggestions please share!

from morphdom.

Yeah it's not really an issue with my use cases, I just thought I would call it out.

Feel free to close the issue if you're fine with the state of things.

from morphdom.

Sounds good. I will close this issue, but we can always reevaluate later. Thanks.

from morphdom.