-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
fix: bring eslint + TS issues to zero #1013
Changes from all commits
4401b7e
ff06d8f
13582e0
8007976
9ea271f
aa736c8
ba18986
5e9bb18
d0fac4a
d504266
2905230
3055a54
9873a0b
265e719
41a3a09
ae2b94f
d367353
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,7 +26,7 @@ export default [ | |
"no-var": "warn", | ||
"prefer-const": "warn", | ||
"no-console": "warn", | ||
"@typescript-eslint/no-explicit-any": "warn", | ||
"@typescript-eslint/no-explicit-any": "error", | ||
"@typescript-eslint/no-unused-vars": [ | ||
"warn", | ||
{ | ||
himanshu-dixit marked this conversation as resolved.
Show resolved
Hide resolved
himanshu-dixit marked this conversation as resolved.
Show resolved
Hide resolved
himanshu-dixit marked this conversation as resolved.
Show resolved
Hide resolved
himanshu-dixit marked this conversation as resolved.
Show resolved
Hide resolved
himanshu-dixit marked this conversation as resolved.
Show resolved
Hide resolved
Comment on lines
26
to
32
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔨 Refactor: Actionable Steps:
This change is beneficial for long-term code quality but requires careful implementation to avoid disrupting the development workflow. 🚀 |
||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Evaluate Impact of Linting Rule Change
The change from 'warn' to 'error' for the
@typescript-eslint/no-explicit-any
rule increases the strictness of the linting configuration. This could lead to build failures or prevent code commits if the 'any' type is used.📌 Recommendation: If the team is not ready for this level of strictness, consider keeping it as a 'warn' and gradually refactor the codebase to reduce 'any' usage before enforcing it as an 'error'.