Urara-Blog/node_modules/.pnpm-store/v3/files/81/adbd25055258db0fc2971f0027f7ac089054f366adb2b8548fd07b133275cb265321055c9b65f6771f148d37ca1463313e1ce63d8ea112436e15d17356ed12
2022-08-14 01:14:53 +08:00

117 lines
2.9 KiB
Text

---
description: 'Enforce unbound methods are called with their expected scope.'
---
> 🛑 This file is source code, not the primary documentation location! 🛑
>
> See **https://typescript-eslint.io/rules/unbound-method** for documentation.
Class functions don't preserve the class scope when passed as standalone variables.
If your function does not access `this`, [you can annotate it with `this: void`](https://www.typescriptlang.org/docs/handbook/2/functions.html#declaring-this-in-a-function), or consider using an arrow function instead.
If you're working with `jest`, you can use [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md) to lint your test files, which knows when it's ok to pass an unbound method to `expect` calls.
## Rule Details
Examples of code for this rule
<!--tabs-->
### ❌ Incorrect
```ts
class MyClass {
public log(): void {
console.log(this);
}
}
const instance = new MyClass();
// This logs the global scope (`window`/`global`), not the class instance
const myLog = instance.log;
myLog();
// This log might later be called with an incorrect scope
const { log } = instance;
// arith.double may refer to `this` internally
const arith = {
double(x: number): number {
return x * 2;
},
};
const { double } = arith;
```
### ✅ Correct
```ts
class MyClass {
public logUnbound(): void {
console.log(this);
}
public logBound = () => console.log(this);
}
const instance = new MyClass();
// logBound will always be bound with the correct scope
const { logBound } = instance;
logBound();
// .bind and lambdas will also add a correct scope
const dotBindLog = instance.logBound.bind(instance);
const innerLog = () => instance.logBound();
// arith.double explicitly declares that it does not refer to `this` internally
const arith = {
double(this: void, x: number): number {
return x * 2;
},
};
const { double } = arith;
```
## Options
The rule accepts an options object with the following property:
- `ignoreStatic` to not check whether `static` methods are correctly bound
### `ignoreStatic`
Examples of **correct** code for this rule with `{ ignoreStatic: true }`:
```ts
class OtherClass {
static log() {
console.log(OtherClass);
}
}
// With `ignoreStatic`, statics are assumed to not rely on a particular scope
const { log } = OtherClass;
log();
```
## Example
```json
{
"@typescript-eslint/unbound-method": [
"error",
{
"ignoreStatic": true
}
]
}
```
## When Not To Use It
If your code intentionally waits to bind methods after use, such as by passing a `scope: this` along with the method, you can disable this rule.
If you're wanting to use `toBeCalled` and similar matches in `jest` tests, you can disable this rule for your test files in favor of [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md).