Why does listeners.onChange fire after field.removeValue() or field.moveValue() ?

[pedro757]

listeners.onChange happens to be fired after field.removeValue() and field.moveValue(), effectively running the onChange function on the next array item, which is weird and intuitive.

1. I have a table with two columns if I change one column there's a listener that resets the other field.
2. But If there are many rows in table and I delete the first element, it will reset the next row columns, because listeners.onChange happens to be fired after the field.removeValue()

This makes it difficult to work with fieldComponents.

[LeCarbonator]

field.removeValue() and field.moveValue() change the data of field, so it triggers the onChange listener. This is usually what you want, but it does sound like this is not one of those cases.

Modify your calls to avoid running them:

field.removeValue(myIndex, { dontRunListeners: true });
field.moveValue(source, destination, { dontRunListeners: true});