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.
For consistency reasons and future proofing filters should be defined as angular.filter(name, function) instead of just assigning directly to angular.filter.
Right now it's confusing that this is the only place you directly assign while service, widget, directive, markup and the rest use an extensionMap function.
The text was updated successfully, but these errors were encountered:
Agree on that. angular.filter() is built by extensionMap() as well, so it's only about changing the code:
angular.filter.name -->> angular.filter(name, function(){});
For consistency reasons and future proofing filters should be defined as angular.filter(name, function) instead of just assigning directly to angular.filter.
Right now it's confusing that this is the only place you directly assign while service, widget, directive, markup and the rest use an extensionMap function.
The text was updated successfully, but these errors were encountered: