You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: checking a single-choice child always triggers 2 events:
the newly checked option event
the unchecked event of the previously checked option
Fixing this requires to evaluate sending the model-value-changed event asynchronously, and then we can compute our values based on all children events (the test above would run).
But... by doing this (evaluating async) related select-rich / listbox tests that depend on synchronicity fail. It might be breaking in other contexts as well.
So it’s better to schedule till a refactor for v1: make parent group responsible for all bookkeeping, without waiting for children
events. This will be better for readibility, maintainability and performance.
Expected behavior
changedProperties in
updated
should containmodelValue
only when array contents differActual Behavior
It will probably fail on case 1 below.
Make a test that reflects #1026 (comment)
Assume we have a group with checkedIndex
[0,1,4]
So spy on changedProperties and see if modelValue detects a change when:
this.checkedIndex = [0,1,4]
-> array ref changed, although we DO NOT expect it to be picked up inupdated
this.checkedIndex.push(2)
-> array ref didn't change, but we DO expect it to be picked up inupdated
The text was updated successfully, but these errors were encountered: