Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not so opinionated analog of `rxjs-prefer-angular-takeuntil`, please

See original GitHub issue

I’d like to suggest an idea of a bit less restrictive analog of rxjs-prefer-angular-takeuntil.

Since there are a plenty of libraries offering some automation for creating and completing destroy subjects (https://www.npmjs.com/search?q=take until destroyed), I’d like to have a rule that only checks that .subscribe() in component is preceded by .takeUntil() (or any of its configurable aliases) in .pipe(). And doesn’t check destroy subject, ngOnDestroy(), .next() and .complete() calls, and whatever else rxjs-prefer-angular-takeuntil currently checks.

Perhaps, might be achieved by adding more options to existing rxjs-prefer-angular-takeuntil rule. Or by implementing a completely separate new rule. What do you think?