Skip to content

Conversation

@mainframev
Copy link
Contributor

@mainframev mainframev commented Sep 15, 2025

PR Checklist

Overview

This is a follow-up on #11197. The fix was originally implemented in #11359, but was inadvertently overwritten during conflict resolution and never made it into the release. We have a patch in our codebase with this change. Without this fix, our lint task enters an infinite loop both locally and on CI

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @mainframev!

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.

@netlify
Copy link

netlify bot commented Sep 15, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 73c5e51
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/68c950b3d416340008b88670
😎 Deploy Preview https://deploy-preview-11605--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 96 (🟢 up 9 from production)
Accessibility: 97 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@nx-cloud
Copy link

nx-cloud bot commented Sep 15, 2025

View your CI Pipeline Execution ↗ for commit 73c5e51

Command Status Duration Result
nx test eslint-plugin --coverage=false ✅ Succeeded 5m 10s View ↗
nx run-many -t lint ✅ Succeeded 3m 10s View ↗
nx run-many -t typecheck ✅ Succeeded 2m 5s View ↗
nx run integration-tests:test ✅ Succeeded 7s View ↗
nx test eslint-plugin-internal --coverage=false ✅ Succeeded 4s View ↗
nx test typescript-estree --coverage=false ✅ Succeeded 2s View ↗
nx run types:build ✅ Succeeded 6s View ↗
nx run generate-configs ✅ Succeeded 9s View ↗
Additional runs (27) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-09-16 12:09:51 UTC

@mainframev
Copy link
Contributor Author

@JoshuaKGoldberg 👋🏻

In my previous PR, I accidentally overwrote an important change and only noticed after it was merged. Should I open a separate issue to track this?

@codecov
Copy link

codecov bot commented Sep 15, 2025

Codecov Report

❌ Patch coverage is 80.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.91%. Comparing base (85d8dea) to head (73c5e51).
⚠️ Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
packages/eslint-plugin/src/rules/no-deprecated.ts 80.00% 3 Missing ⚠️

❌ Your patch check has failed because the patch coverage (80.00%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11605      +/-   ##
==========================================
- Coverage   90.92%   90.91%   -0.01%     
==========================================
  Files         506      506              
  Lines       51325    51345      +20     
  Branches     8469     8474       +5     
==========================================
+ Hits        46665    46682      +17     
- Misses       4647     4650       +3     
  Partials       13       13              
Flag Coverage Δ
unittest 90.91% <80.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
packages/eslint-plugin/src/rules/no-deprecated.ts 96.36% <80.00%> (-0.79%) ⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mainframev mainframev force-pushed the fix/no-deprecated-perf-issue branch from 7b612eb to 7dee4dc Compare September 15, 2025 17:16
@mainframev mainframev force-pushed the fix/no-deprecated-perf-issue branch from 7dee4dc to 73c5e51 Compare September 16, 2025 11:57
@JoshuaKGoldberg
Copy link
Member

@JoshuaKGoldberg 👋🏻

In my previous PR, I accidentally overwrote an important change and only noticed after it was merged. Should I open a separate issue to track this?

If you don't mind, yes please! We don't often look at draft PRs. I'll go ahead and review this one now in the meantime.

let current = symbol;

while (tsutils.isSymbolFlagSet(current, ts.SymbolFlags.Alias)) {
/* istanbul ignore next */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This'll need to be unit tested.

(I'm guessing you know this as a repeat contributor 😄 but just noting for tracking / in case someone else picks up this work)

Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@JoshuaKGoldberg
Copy link
Member

👋 @mainframev are you waiting on us for anything with this PR?

@mainframev
Copy link
Contributor Author

@JoshuaKGoldberg

Thanks, no, everything is clear, I need to add proper test for this scenario and create issue. I'll get back to it asap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants