Urara-Blog/node_modules/.pnpm-store/v3/files/70/2a8fdb09bed4e5a6075473da6bd7d1457788848880502311edd584a8f83b93bd484a7ee4b6803667d2b8b3b508ae4cf50b04e402868b95181f34579d4ba272
2022-08-14 01:14:53 +08:00

100 lines
1.8 KiB
Text

---
description: 'Enforce using function types instead of interfaces with call signatures.'
---
> 🛑 This file is source code, not the primary documentation location! 🛑
>
> See **https://typescript-eslint.io/rules/prefer-function-type** for documentation.
## Rule Details
This rule suggests using a function type instead of an interface or object type literal with a single call signature.
Examples of code for this rule:
<!--tabs-->
### ❌ Incorrect
```ts
interface Foo {
(): string;
}
```
```ts
function foo(bar: { (): number }): number {
return bar();
}
```
```ts
interface Foo extends Function {
(): void;
}
```
```ts
interface MixinMethod {
// returns the function itself, not the `this` argument.
(arg: string): this;
}
```
### ✅ Correct
```ts
interface Foo {
(): void;
bar: number;
}
```
```ts
function foo(bar: { (): string; baz: number }): string {
return bar();
}
```
```ts
interface Foo {
bar: string;
}
interface Bar extends Foo {
(): void;
}
```
```ts
// returns the `this` argument of function, retaining it's type.
type MixinMethod = <TSelf>(this: TSelf, arg: string) => TSelf;
// a function that returns itself is much clearer in this form.
type ReturnsSelf = (arg: string) => ReturnsSelf;
```
```ts
// multiple call signatures (overloads) is allowed:
interface Overloaded {
(data: string): number;
(id: number): string;
}
// this is equivelent to Overloaded interface.
type Intersection = ((data: string) => number) & ((id: number) => string);
```
## Options
```jsonc
// .eslintrc.json
{
"rules": {
"@typescript-eslint/prefer-function-type": "warn"
}
}
```
This rule is not configurable.
## When Not To Use It
If you specifically want to use an interface or type literal with a single call signature for stylistic reasons, you can disable this rule.