-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(eslint-plugin): [no-deprecated] should allow ignoring of deprecated value #10670
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(eslint-plugin): [no-deprecated] should allow ignoring of deprecated value #10670
Conversation
Thanks for the PR, @y-hsgw! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
View your CI Pipeline Execution ↗ for commit 3b3b72a
☁️ Nx Cloud last updated this comment at |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10670 +/- ##
==========================================
+ Coverage 90.84% 90.85% +0.01%
==========================================
Files 501 501
Lines 50919 50978 +59
Branches 8387 8407 +20
==========================================
+ Hits 46256 46315 +59
Misses 4648 4648
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
✨
Whoops, wrong button, sorry for the noise :)
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.
Thanks for sending this in! 💪
Codecov is right to report, we have tests set up in packages/type-utils
to make sure these utils are fully unit tested. Could you please add tests to TypeOrValueSpecifier.test.ts
?
All three of the specifier sources formats should be tested: file, lib, and package.
I've added the tests! |
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.
Do you think it might be necessary to verify whether it is imported from a package?
Indeed I do - the goal of the shared format is to match on both the name and where a type/value is declared.
Thanks!
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.
A bit more complication! 🚀
I'm also starting to wonder - maybe it makes sense to unify the typeMatchesSpecifier
and valueMatchesSpecifier
logic? If the value checking needs type information anyway...
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.
I think this is in good shape!
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.
This is great, thank you! 🙌 I'm very excited to see this land.
return typeof specifierName === 'string' ? [specifierName] : specifierName; | ||
}; | ||
|
||
const getStaticName = (node: TSESTree.Node): string | undefined => { |
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.
[Non-Actionable] I'm surprised we don't already have a function like this somewhere 😄. I spent a bit searching and couldn't find one. The closest was getNameFromMember
over in eslint-plugin
but it's not quite the same. Ah well.
The CI unit testing failure is unrelated flake. |
d1388fc
into
typescript-eslint:main
PR Checklist
Overview
I have created a
valueMatchesSomeSpecifier
function to check if a value matches the specified specifiers. However, this implementation might only cover the specific case related to the bug in this issue.If you have any advice or suggestions, please feel free to share.
💪