Proposal

{
  "rules": {
    "@typescript-eslint/prefer-enum-initializers ": ["off"]
  }
}

Proposal Result

The name and message are just an example.

Actual Result

n/a

Additional Info

Enum infers sequential numbers automatically when initializers are omitted:

enum Status {
  Open, // infer 0
  Closed, // infer 1
}

declare const updateStatus: (value: Status) => void

updateStatus(0) // same as updateStatus(Status.Open)

With this approach, if new values are declared without following the existing order and the value of the enum has been saved in an external source, we will have inconsistencies between the saved value and the new representation, example:

enum Status {
  Idle, // new value
  Open,
  Closed,
}

type Resource = { status: Status }

const resource = findResource(id) // previous have { status: Status.Open }

resource.status === Idle // returns true

And removing an option from the enum is not possible, unless it is the last option in the enum, otherwise the order will break as well.

For the my current company's eslint-preset we've implemented a simple version of this rule here. As dealing with enums in typescript can have its trade-offs, I'd like to know if this would be useful to others.

Oh and thanks for the great work with all these packages! They are being extremely useful and effective in guaranteeing the quality of our code 😁 🙌