typescript/no-mixed-enums Pedantic

🚧 An auto-fix is still under development.

What it does

This rule disallows enums from having both string and numeric members.

Why is this bad?

TypeScript enums can have string, numeric, or computed members. Having mixed string and numeric members in the same enum can lead to confusion and unexpected runtime behavior due to how TypeScript compiles enums.

Examples

Examples of incorrect code for this rule:

enum Status {
  Open = 1,
  Closed = "closed",
}

enum Direction {
  Up = "up",
  Down = 2,
  Left = "left",
  Right = 4,
}

Examples of correct code for this rule:

// All numeric
enum Status {
  Open = 1,
  Closed = 2,
}

// All string
enum Direction {
  Up = "up",
  Down = "down",
  Left = "left",
  Right = "right",
}

// Auto-incremented numeric
enum Color {
  Red,
  Green,
  Blue,
}

How to use

To enable this rule in the CLI or using the config file, you can use:

CLI

oxlint --deny typescript/no-mixed-enums

Config (.oxlintrc.json)

{
  "rules": {
    "typescript/no-mixed-enums": "error"
  }
}

References

• Rule Source