-
Notifications
You must be signed in to change notification settings - Fork 130
angular/on-watch error #231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Documentation: https://docs.angularjs.org/api/ng/type/$rootScope.Scope - Returns a deregistration function for this listener.
http://stackoverflow.com/questions/25113884/should-angular-watch-be-removed-when-scope-destroyed |
@tilmanpotthof Thank you very much! |
Does this really make sense? Shouldn't this lint ignore the |
I would love to submit a PR if this behaviour is not wanted |
@gitnik Good point. I think unsubscribing from the $rootScope does not make sense, at least with the ... or did I miss something? @remcohaszing @Gillespie59 |
Seems legit. |
OK I will submit a PR then :-) |
Shouldn't this actually only lint |
👍 |
Any reason not to do this?
|
hi,guys
How do I fix this error?
Error Messages:
Corresponding Source:
The text was updated successfully, but these errors were encountered: