astro-ghostcms/.pnpm-store/v3/files/4e/9a7605534d62d99234c986b4e07...

164 lines
3.4 KiB
Plaintext

---
description: 'Enforce constituents of a type union/intersection to be sorted alphabetically.'
---
> 🛑 This file is source code, not the primary documentation location! 🛑
>
> See **https://typescript-eslint.io/rules/sort-type-constituents** for documentation.
Sorting union (`|`) and intersection (`&`) types can help:
- keep your codebase standardized
- find repeated types
- reduce diff churn
This rule reports on any types that aren't sorted alphabetically.
> Types are sorted case-insensitively and treating numbers like a human would, falling back to character code sorting in case of ties.
## Examples
<!--tabs-->
### ❌ Incorrect
```ts
type T1 = B | A;
type T2 = { b: string } & { a: string };
type T3 = [1, 2, 4] & [1, 2, 3];
type T4 =
| [1, 2, 4]
| [1, 2, 3]
| { b: string }
| { a: string }
| (() => void)
| (() => string)
| 'b'
| 'a'
| 'b'
| 'a'
| readonly string[]
| readonly number[]
| string[]
| number[]
| B
| A
| string
| any;
```
### ✅ Correct
```ts
type T1 = A | B;
type T2 = { a: string } & { b: string };
type T3 = [1, 2, 3] & [1, 2, 4];
type T4 =
| A
| B
| number[]
| string[]
| any
| string
| readonly number[]
| readonly string[]
| 'a'
| 'a'
| 'b'
| 'b'
| (() => string)
| (() => void)
| { a: string }
| { b: string }
| [1, 2, 3]
| [1, 2, 4];
```
## Options
### `checkIntersections`
Whether to check intersection types (`&`).
Examples of code with `{ "checkIntersections": true }` (the default):
<!--tabs-->
#### ❌ Incorrect
```ts option='{ "checkIntersections": true }'
type ExampleIntersection = B & A;
```
#### ✅ Correct
```ts option='{ "checkIntersections": true }'
type ExampleIntersection = A & B;
```
### `checkUnions`
Whether to check union types (`|`).
Examples of code with `{ "checkUnions": true }` (the default):
<!--tabs-->
#### ❌ Incorrect
```ts option='{ "checkUnions": true }'
type ExampleUnion = B | A;
```
#### ✅ Correct
```ts option='{ "checkUnions": true }'
type ExampleUnion = A | B;
```
### `groupOrder`
Each constituent of the type is placed into a group, and then the rule sorts alphabetically within each group.
The ordering of groups is determined by this option.
- `conditional` - Conditional types (`A extends B ? C : D`)
- `function` - Function and constructor types (`() => void`, `new () => type`)
- `import` - Import types (`import('path')`)
- `intersection` - Intersection types (`A & B`)
- `keyword` - Keyword types (`any`, `string`, etc)
- `literal` - Literal types (`1`, `'b'`, `true`, etc)
- `named` - Named types (`A`, `A['prop']`, `B[]`, `Array<C>`)
- `object` - Object types (`{ a: string }`, `{ [key: string]: number }`)
- `operator` - Operator types (`keyof A`, `typeof B`, `readonly C[]`)
- `tuple` - Tuple types (`[A, B, C]`)
- `union` - Union types (`A | B`)
- `nullish` - `null` and `undefined`
For example, configuring the rule with `{ "groupOrder": ["literal", "nullish" ]}`:
<!--tabs-->
#### ❌ Incorrect
```ts option='{ "groupOrder": ["literal", "nullish" ]}'
type ExampleGroup = null | 123;
```
#### ✅ Correct
```ts option='{ "groupOrder": ["literal", "nullish" ]}'
type ExampleGroup = 123 | null;
```
## When Not To Use It
This rule is purely a stylistic rule for maintaining consistency in your project.
You can turn it off if you don't want to keep a consistent, predictable order for intersection and union types.
However, keep in mind that inconsistent style can harm readability in a project.