-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(eslint-plugin): [no-shadow] fix false-positive on enum declaration #2374
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
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
Codecov Report
@@ Coverage Diff @@
## v4 #2374 +/- ##
=======================================
Coverage 92.98% 92.99%
=======================================
Files 286 286
Lines 9041 9046 +5
Branches 2515 2517 +2
=======================================
+ Hits 8407 8412 +5
Misses 304 304
Partials 330 330
Flags with carried forward coverage won't be shown. Click here to find out more.
|
did this regress or is it not released yet? all enums report |
@bradennapier You may need to set the following rules: 'no-shadow': 'off',
'@typescript-eslint/no-shadow': ['error'], |
It's unfortunate that the changelog does not indicate that the Not sure if this is something you want to address, but as more people make the switch to v4 I think it would help to have the changelog show that there is a new rule that replaces eslint's There have already been several issues created because users don't know that the new rule is available when they upgrade. |
The changelog is just an auto-generated log of commits bundled in each release. Prefer the github release notes which are curated and explain in detail: I'll add a link to this doc. I kinda want to just delete these files though as they're just noise.
There's a larger problem with users not using the search. It's a huge problem with github as a whole. |
Totally makes sense. I just didn't realize that was where I needed to look, and apparently at least a few other people had the same problem, so I thought I would point it out :) |
Fixes #2360