-
Notifications
You must be signed in to change notification settings - Fork 26.3k
fix(forms): Don't send updates for identical input values #55761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0db415b
to
efada8d
Compare
In case an input event sends the same value to our forms, we will discard the update and consider the input hasn't change. This will prevent having duplicate values on the valueChanges event. Fixes angular#43228
efada8d
to
2c6cd7e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code-wise this LGTM. It will definitely require a TGP though, and I could see it being quite breaking.
In TGP (train): OCL:688303046:BASE:688537051:1729617073387:be2fcd5 |
As expected, TGP revealed some breakages, though less than expected. The errors seem to indicate patterns where identical (===) objects are passed but have deep mutations. Dropping this from v19 for now and will follow up with @JeanMeche. |
I'll close it as this is probably too breaking. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In case an input event sends the same value to our forms, we will discard the update and consider the input hasn't change. This will prevent having duplicate values on the valueChanges event.
Fixes #43228
Note: Seing how this change broke our tests, I have low confidence we'll be able to merge it.