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 Oct 2, 2019. It is now read-only.
When filtering or changing the array of items externally (by either adding or removing items), all the items are re-rendered. This happens because of the GroupNgRepeatExpression. Groups are tracked by $$hashKey and new groups are created whenever the array changes.
A solution would be to track groups by group name, since it is unique by definition. This can produce a significant performance improvement for large arrays of items. Is there any I am overlooking for which "track by $group.name" is not an option?
The text was updated successfully, but these errors were encountered:
Use "track by" to track groups of choices by their name instead of
the $$hastKey. This way, existing items don't have to be
re-rendered when the array of items changes.
Closesangular-ui#1721
When filtering or changing the array of items externally (by either adding or removing items), all the items are re-rendered. This happens because of the GroupNgRepeatExpression. Groups are tracked by $$hashKey and new groups are created whenever the array changes.
A solution would be to track groups by group name, since it is unique by definition. This can produce a significant performance improvement for large arrays of items. Is there any I am overlooking for which "track by $group.name" is not an option?
The text was updated successfully, but these errors were encountered: