fix(eslint-plugin): [no-unnecessary-type-assertion] avoid remove const casting on template literals with expressions inside#8740
Conversation
|
Thanks for the PR, @marcalexiei! 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 site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8740 +/- ##
=======================================
Coverage 87.38% 87.39%
=======================================
Files 254 254
Lines 12489 12492 +3
Branches 3919 3920 +1
=======================================
+ Hits 10914 10917 +3
Misses 1304 1304
Partials 271 271
Flags with carried forward coverage won't be shown. Click here to find out more.
|
…t casting on template literals with expressions inside
1ecaf50 to
e29f5cf
Compare
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Ha, tricky stuff - thanks!
And appreciated on the appreciation note. 😁
…t casting on template literals with expressions inside (typescript-eslint#8740)
…t casting on template literals with expressions inside (typescript-eslint#8740)

PR Checklist
Overview
no-unnecessary-type-assertionnow avoids to removeconstcasting from template literals when they are containing expressions.This scenario is handled inside
isConstVariableDeclarationwhich has been renamed toisLiteralVariableDeclarationChangingTypeWithConstto better reflect its purpose.Edit: missed appreciation note... sorry
😅