We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We see people setting enum keys in const-style sometimes, but would prefer to standardise around the approach used in docs.
This can be set via: https://typescript-eslint.io/rules/naming-convention
Incorrect
enum Colors { RED = 'rgb(255, 0, 0)', NOT_RED = 'rgb(0, 255, 255)', } enum COLORS { /* ... */ }
Correct
enum Colors { Red = 'rgb(255, 0, 0)', NotRed = 'rgb(0, 255, 255)', }
See:
The text was updated successfully, but these errors were encountered:
feat(eslint): enforce consistent enum casing
f9baad3
Resolves #34
9ad3d7d
562f9e9
5b7ca90
21cc24a
🎉 This issue has been resolved in version 4.0.0-canary.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
🎉 This issue has been resolved in version 4.0.0 🎉
No branches or pull requests
We see people setting enum keys in const-style sometimes, but would prefer to standardise around the approach used in docs.
This can be set via: https://typescript-eslint.io/rules/naming-convention
Incorrect
Correct
See:
The text was updated successfully, but these errors were encountered: