fix: already init component

[Matsa59]

Currently we defined if a mutation is a move operation if the node is in the addedNodes and in the removedNodes.

However in some case, an element is added, removed and added again. So it should considered as add + move operations. But alpine will ignore it, considering it as a move operation only (so nothing will be init).

The PR focus on introducing a new state _x_isInit that will be true for component that are initialized.

Also it may speed up a little bit the onMutate function. Previously we checked every deleted nodes before adding any new nodes. For big mutations, iterate over the deletedNodes several times could be CPU intensive.

Conversation on : #3947

[ekwoka]

Should probably handle tracking initialization tracking in the initialization process, not the mutation process.

[Matsa59]

FINALLY I found a way to make it works ... waiting for CI to be sure

Thx @ekwoka for your time and help, really appreciated

[calebporzio]

Thanks! I do think the implementation is a little heavy handed. I instead just changed the addedNodes and removedNodes to JS Sets instead of arrays so that they enforce uniqueness in the case of duplicate addeds and removes. Thanks!

[ekwoka]

Does that solve the actual issue this is meant to solve?

It still will incorrectly consider an element that is added and immediately moved as being a "moved" element and never initialize it, which was the issue.

[Matsa59]

Thanks! I do think the implementation is a little heavy handed. I instead just changed the addedNodes and removedNodes to JS Sets instead of arrays so that they enforce uniqueness in the case of duplicate addeds and removes. Thanks!

It was my first though but it was more complex and didn't fix well the issue :/

[SimoTod]

@Matsa59 I think this change caused #3994