Add more typescript-eslint rules #7
Closed
onemen
started this conversation in
ESLint Suggestion
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? |
0 replies
|
You are more experience, I would like to get your opinion. |
1 reply
|
these are some rules that I think should be enabled for typescript in strict mode |
1 reply
|
Thank you for the suggestions! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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-eslintrecommended-configurations
currently you only use
@typescript-eslint/no-unused-varsand@typescript-eslint/consistent-type-importsFor example, linting
epic-stackwith strict-type-checked and stylistic-type-checked result with 1014 errors.I know that
typescript-eslintstrict configurations are opinionated but I would like to here your opinion on this.Issue Likelihood
typescript-eslintrecommendation is to use one of its recommended configurationsIssue Severity
same as above
Additional Context
Using the above command in
epic-stackfolder show that the current eslint configuration using only 19 rules in total.All reactions