Rule for warning about using `throw` in `catch` functions

I have a suggestion for a rule that would be very useful for me. I'd like to know if a contributor is using `throw` inside a $q `catch` implementation and suggest they use `return $q.reject` instead. The problem with throw with $q is that Angular's implementation always sends what's thrown to the $exceptionHandler even when it's caught later whereas `$q.reject` doesn't.