refactor(rules): merge Angular subscription lifetime rules
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e8cdcec629
commit
569f55dd0d
1 file changed
+1
-3
@@ -5,9 +5,7 @@
|
|||||||
* Prefer declarative observable pipelines.
|
* Prefer declarative observable pipelines.
|
||||||
* Avoid nested `subscribe`.
|
* Avoid nested `subscribe`.
|
||||||
* Avoid manual subscriptions where `async`, signals or framework helpers are sufficient.
|
* Avoid manual subscriptions where `async`, signals or framework helpers are sufficient.
|
||||||
* Prefer `takeUntilDestroyed` or equivalent Angular lifecycle integration for manual subscriptions.
|
* Bind every manual subscription's lifetime with `takeUntilDestroyed` or equivalent Angular lifecycle integration to avoid leaks.
|
||||||
* Always consider subscription lifetime.
|
|
||||||
* Avoid memory leaks from unmanaged subscriptions.
|
|
||||||
* Use the correct flattening operator for the required semantics.
|
* Use the correct flattening operator for the required semantics.
|
||||||
* Do not use `switchMap`, `mergeMap`, `concatMap` or `exhaustMap` interchangeably.
|
* Do not use `switchMap`, `mergeMap`, `concatMap` or `exhaustMap` interchangeably.
|
||||||
* Avoid unnecessary `Subject` usage.
|
* Avoid unnecessary `Subject` usage.
|
||||||
|
|||||||
Reference in new issue
Block a user