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 was archived by the owner on Apr 12, 2024. It is now read-only.
189461f caused an issue with nested literal objects/arrays in ng-class (#15905), essentially because it allowed the expression inputs (a watch optimization) to be used properly in the case of literals with interceptorFns.
Instead of reverting 189461f, or changing ng-class to use deep watch, or declaring its interceptor as $stateful - I'd like to drop nested object/array support from ng-class. This will align ng-class with the Angular version, should improve performance, should simplify the ng-class code a bit.
This would be a breaking change in 1.7.
Any strong objections? Strong use cases for nested objects/arrays in ng-class?