I noticed an issue where I have a list of items where each list has a button that opens a dialog, and forwards a data context.
This data context is put in a data-attribute, stringified in the helper.
When the button is clicked, the dialog opens for the data context and its context is available by accesing node.data(‘attributename’). Here it automatically gets parsed to a object.
This is where it goes wrong, if you remove elements from the list in the order:
Remove item 2
Try remove item 3
When you try to remove item 3, it gets the parsed object of number 2, which doesnt exist anymore. When you look int the source you see the correct JSON for item 3. However, the parsed object is from number 2.
If can demonstrate this issue in the test I build:
Anyone of the Blaze team who wants to take a look?