-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix the scoping of our ESLint rules #13558
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13558 +/- ##
==========================================
+ Coverage 59.74% 59.77% +0.02%
==========================================
Files 670 670
Lines 37427 37497 +70
Branches 5371 5385 +14
==========================================
+ Hits 22359 22412 +53
- Misses 13905 13916 +11
- Partials 1163 1169 +6
Continue to review full report at Codecov.
|
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.
Why not enable for all new files.
Update this file to include all existing files, this way all new files will always have to be eslint compliant, else we'd be updating this file for each new file/folder we add.
@DonJayamanne after talking with @brettcannon we don't want to enable it for the entire repo just yet as we want to prioritize the component refactoring work. We can/will spend time fixing warnings and refactoring code in the rest of the repo once we're done 🙂 |
Not sure what you mean by that. What I'm suggesting is
This way new code will be eslint compliant, which in my opinion is a much smaller work than having to do that later on again... This is exactly what we did to ensure the code base was using strict types when we migrated (slowly) to strict checks in tsconfig (tsc). |
Oh I see! Yeah we could do that, although that would be a lot of files lol |
I'm fine with enumerating all the files outside of our refactoring work so that any new files automatically get caught by this. |
Sounds good, this PR is not ready for review then. |
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.
LGTM
Kudos, SonarCloud Quality Gate passed!
|
Alright, PR ready for review for real this time. @ericsnowcurrently could you take a look at it again? What changed is that now we are listing all of our js, ts, jsx and tsx files in |
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.
LGTM
For #13142
vscode-python/src/
andvscode-python/build
except forsrc/client/pythonEnvironments
andsrc/test/pythonEnvironments
ipywidget
workspace folder (was causing issues)src/client/pythonEnvironments
andsrc/test/pythonEnvironments
in.prettierignore
package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed).