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
{{ message }}
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
If you just think of the user then I think the behavior is that it should update the value in the collection but not recreate the instance. I'm not sure how can implement that though?
Angular can do (1). I'm worried about this, however. I'd like to see how often this comes up and if the workarounds aren't too horrible. Breaking the invariant that template's always create new instances for different model values seems dangerous to me.
i.e.
Seems like the two choices are
Up the element position in the iterated Array. This seems scary, as it will destroy the instance and create a new one
Issue a warning.
The text was updated successfully, but these errors were encountered: