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
What is the motivation / use case for changing the behavior?
Every implementation of Field Array will have to override, call super, and then mark the form as dirty for both Add() and Remove().
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
Adding/Removing records in a custom FieldArrayType does not mark the dirty flag.
Expected behavior
Any user-driven actions will mark a form dirty. Per Angular's #16370, it is the action's responsibility to call markAsDirty().
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/angular-ferxhg
What is the motivation / use case for changing the behavior?
Every implementation of Field Array will have to override, call super, and then mark the form as dirty for both Add() and Remove().
The text was updated successfully, but these errors were encountered: