Enhancement: @typescript-eslint/naming-convention enum values in PascalCase

[Conaclos]

Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Link to the rule's documentation

https://typescript-eslint.io/rules/naming-convention/

Description

As notes in a stackoverflow thread, by default ESLint naming-convention rule enforces camelCase for enum values.

This is really strange because I am not aware of any style guide that encourages this convention. Generally style guide encourages the use of PascalCase or CONSTANT_CASE.

I propose to change the default behavior to PascalCase for enum values.

Note that enum value are also types, this should thus be consistent with the existing defaults.

Fail

enum Direction {
  prev,
  next,
}

Pass

enum Direction {
  Prev,
  Next,
}

Additional Info

No response

[bradzacher]

The default isn't there as a "this is the way to do things for everyone". Instead it's there as a quick proxy for the old camelcase lint rule. It's there as an example to show what you could do with the rule.
Its rare that the default will truly match a codebase's naming convention - in which case they will have to design their own config.

This exact default has been in place for 2 years and this is the first time someone has asked for a change. Either that means that (a) few people use the rule so nobody has noticed, (b) the people that use the rule don't use the default or (c) people are happy with the default.

In either case, I don't see a compelling argument for us to change the default here, given that it is a breaking change for us to change defaults and would be very disruptive to users that rely on them.