-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
🛠️ - Typescript rules against: enums & interfaces #12
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two rules partially go against the grain on what this package was trying to be:
Extended ESLint Rules
The idea behind this config is to enforce consistency across all projects. We've tried to keep the rules as minimal as possible, and for the most part simply inherit from the recommended rules of the plugins we use. The main exceptions are when it comes to the following. Note: We've purposely only defined rules that are auto fixable, these rules should make it easier to write code, and not get in the way.
Can we update the README to reflect the changes too? Would be nice to also explain the reasoning there.
…m/lint into feature/typescript-rules
Added two Typescript specific eslint rules;
no-restricted-syntax - TSEnumDeclaration
- Error when using Enums, let's push foras const
since it's more declarative that it outputs JS.@typescript-eslint/consistent-type-definitions
- Error when using interfaces. The difference between interface and type is minimal and the one additional feature it supports we shouldn't use.Set nvm version to
v18