Add more typescript-eslint rules #7
Replies: 4 comments 2 replies
-
Just because rules exist and the epic stack breaks them does not mean they protect from actual issues that surface in poor user experience. I would like to discuss each rule individually. Could you justify the inclusion of specific rules? |
Beta Was this translation helpful? Give feedback.
-
You are more experience, I would like to get your opinion. |
Beta Was this translation helpful? Give feedback.
-
these are some rules that I think should be enabled for typescript in strict mode
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the suggestions! |
Beta Was this translation helpful? Give feedback.
-
Search Terms Used
typescript-eslint
Rule Docs
https://typescript-eslint.io/users/configs/#recommended-configurations
Suggested Change
Since all all epicweb-dev packages uses typescript, I thing you should consider use some of
typescript-eslint
recommended-configurations
currently you only use
@typescript-eslint/no-unused-vars
and@typescript-eslint/consistent-type-imports
For example, linting
epic-stack
with strict-type-checked and stylistic-type-checked result with 1014 errors.I know that
typescript-eslint
strict configurations are opinionated but I would like to here your opinion on this.Issue Likelihood
typescript-eslint
recommendation is to use one of its recommended configurationsIssue Severity
same as above
Additional Context
Using the above command in
epic-stack
folder show that the current eslint configuration using only 19 rules in total.Beta Was this translation helpful? Give feedback.
All reactions