Disallow passing unbound methods (rxjs-x/no-unbound-methods)
June 5, 2025 · View on GitHub
💼 This rule is enabled in the following configs: ✅ recommended, 🔒 strict.
💭 This rule requires type information.
This rule effects failures if unbound methods are passed as callbacks.
This rule is aware of Angular's Signal type by default
which can be safely passed unbound.
Rule details
Examples of incorrect code for this rule:
return this.http
.get<Something>("https://api.some.com/things/1")
.pipe(
map(this.extractSomeProperty),
catchError(this.handleError)
);
Examples of correct code for this rule:
return this.http
.get<Something>("https://api.some.com/things/1")
.pipe(
map((s) => this.extractSomeProperty(s)),
catchError((e) => this.handleError(e))
);
return this.http
.get<Something>("https://api.some.com/things/1")
.pipe(
map(this.extractSomeProperty.bind(this)),
catchError(this.handleError.bind(this))
);
Options
| Name | Description | Type | Default |
|---|---|---|---|
allowTypes | An array of function types that are allowed to be passed unbound. | String[] | [Signal] |
When Not To Use It
If every handler in your project does not depend on the this context in their implementations,
then in some cases it may be safe to not use this rule.
However, keep in mind that future changes may introduce bugs
by changing their implementations to depend on the this context;
see the linked blog post for best practice explanation.
Type checked lint rules are more powerful than traditional lint rules, but also require configuring type checked linting.