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 Apr 12, 2024. It is now read-only.
One time bindings are great feature. It reduces watchers.
But sometimes You have to change some directives parameters.
Great solution would be to reset directive and force to init directive once more.
The new setting would be in game as well as one time bindings.
Can You think about that?
The text was updated successfully, but these errors were encountered:
Only the directive itself should have the knowledge of and the ability for un-registering watches, which means you'd have to de-register it from within itself. And that means you might as well implement your own initialization function to change the behaviour completely, there is no need to involve Angular's directive repository to do just that.
There is a general consensus that some kind of freezing / un-freezing of watches on scopes would be beneficial, but we can't think of a solution that would work for most / all use-cases and wouldn't be a foot-gun.
One time bindings are great feature. It reduces watchers.
But sometimes You have to change some directives parameters.
Great solution would be to reset directive and force to init directive once more.
The new setting would be in game as well as one time bindings.
Can You think about that?
The text was updated successfully, but these errors were encountered: