useConsistentEnumValueType

Это содержимое пока не доступно на вашем языке.

TypeScript and TSX

Summary

Rule available since: v2.3.13
Diagnostic Category: lint/nursery/useConsistentEnumValueType
This rule doesn’t have a fix.
The default severity of this rule is information.
This rule belongs to the following domains:
- project
Sources:
- Same as @typescript-eslint/no-mixed-enums

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "nursery": {
5
        "useConsistentEnumValueType": "error"
6
      }
7
    }
8
  }
9
}

Description

Disallow enums from having both number and string members.

TypeScript enums are allowed to assign numeric or string values to their members. Most enums contain either all numbers or all strings, but in theory you can mix-and-match within the same enum. Mixing enum member types is generally considered confusing and a bad practice.

Examples

Invalid

1
enum Status {
2
  Unknown,
3
  Closed = 1,
4
  Open = 'open',
5
}

code-block.ts:3:3 lint/nursery/useConsistentEnumValueType ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Inconsistent enum value type.
  
    1 │ enum Status {
    2 │   Unknown,
  > 3 │   Closed = 1,
      │   ^^^^^^^^^^
    4 │   Open = ‘open’,
    5 │ }
  
  ℹ Another inconsistent enum value type.
  
    2 │   Unknown,
    3 │   Closed = 1,
  > 4 │   Open = ‘open’,
      │   ^^^^^^^^^^^^^
    5 │ }
    6 │ 
  
  ℹ Mixing number and string enums can be confusing. Make sure to use a consistent value type within your enum.
  
  ℹ This rule belongs to the nursery group, which means it is not yet stable and may change in the future. Visit https://biomejs.dev/linter/#nursery for more information.

Valid

1
enum Status {
2
  Unknown = 0,
3
  Closed = 1,
4
  Open = 2,
5
}

1
enum Status {
2
  Unknown,
3
  Closed,
4
  Open,
5
}

1
enum Status {
2
  Unknown = 'unknown',
3
  Closed = 'closed',
4
  Open = 'open',
5
}