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
If you have a FormGroup with multiple controls, observing control.rawValue.valueA will emit updates even when just control.rawValue.valueB changed.
The reason is that rawValue is changing whenever any nested value changes, so based on the current implementation this is correct behavior. Still, observing changes to rawValue or value is expected to be common enough that we should optimize for it. Perhaps we should store rawValue and value as nested Solidjs Store objects rather than as memos (for both FormGroup and FormArray). This would allow observing deeply nested children and only getting updates when the observed properties change.
At the moment, you could workaround this issue by, e.g., observing control.controls.valueA.rawValue.
The text was updated successfully, but these errors were encountered:
If you have a FormGroup with multiple controls, observing
control.rawValue.valueA
will emit updates even when justcontrol.rawValue.valueB
changed.The reason is that
rawValue
is changing whenever any nested value changes, so based on the current implementation this is correct behavior. Still, observing changes to rawValue or value is expected to be common enough that we should optimize for it. Perhaps we should storerawValue
andvalue
as nested SolidjsStore
objects rather than as memos (for both FormGroup and FormArray). This would allow observing deeply nested children and only getting updates when the observed properties change.At the moment, you could workaround this issue by, e.g., observing
control.controls.valueA.rawValue
.The text was updated successfully, but these errors were encountered: