Skip to content

fix(rule-tester): normalize paths before checking if they escape cwd - #11525

Merged
JoshuaKGoldberg merged 3 commits into
typescript-eslint:mainfrom
dbarabashh:fix/rule-tester-normalize-paths
Sep 3, 2025
Merged

JoshuaKGoldberg merged 3 commits into
typescript-eslint:mainfrom
dbarabashh:fix/rule-tester-normalize-paths

Conversation

@dbarabashh

@dbarabashh dbarabashh commented Aug 23, 2025 •

Copy link
Copy Markdown
Contributor

PR Checklist

Overview

Paths like './../../file.ts' were not being detected as escaping the current directory because the check only looked for paths starting with '..' . This fix normalizes paths before checking, so paths like './../' and './../../' are properly handled.

@typescript-eslint

Copy link
Copy Markdown
Contributor

Thanks for the PR, @dbarabashh!

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

netlify Bot commented Aug 23, 2025 •

Copy link
Copy Markdown

✅ Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 6ff0c5a
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/68b0af658047ff00085892ce
😎 Deploy Preview https://deploy-preview-11525--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: 97 (no change 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

nx-cloud Bot commented Aug 23, 2025 •

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit 6ff0c5a

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

☁️ Nx Cloud last updated this comment at 2025-08-28 19:45:59 UTC

@dbarabashh

Copy link
Copy Markdown
Contributor Author

Not very sure if this is the same problem as in the previous PR. But it looks like it is coming from the main branch and needs to be fixed. @JoshuaKGoldberg, @kirkwaiblinger wdyt?

@codecov

codecov Bot commented Aug 27, 2025 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.87%. Comparing base (31a7336) to head (6ff0c5a).
⚠️ Report is 24 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #11525   +/-   ##
=======================================
  Coverage   90.87%   90.87%           
=======================================
  Files         505      505           
  Lines       51146    51146           
  Branches     8424     8424           
=======================================
  Hits        46480    46480           
  Misses       4652     4652           
  Partials       14       14           
Flag Coverage Δ
unittest 90.87% <100.00%> (ø)

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

Files with missing lines Coverage Δ
packages/rule-tester/src/RuleTester.ts 73.78% <100.00%> (ø)
🚀 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.

@kirkwaiblinger kirkwaiblinger left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good! just requesting a testing tweak

Comment thread packages/rule-tester/tests/filename.test.ts

@kirkwaiblinger kirkwaiblinger left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Lovely, thanks!

@kirkwaiblinger kirkwaiblinger added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Aug 29, 2025

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

✨

@JoshuaKGoldberg
JoshuaKGoldberg merged commit 9529ac1 into typescript-eslint:main Sep 3, 2025
@dbarabashh

Copy link
Copy Markdown
Contributor Author

🚀

hugop95 pushed a commit to hugop95/typescript-eslint that referenced this pull request Aug 14, 2026
…ypescript-eslint#11525)

* fix(rule-tester): normalize paths before checking if they escape cwd

* added test cases

---------

Co-authored-by: Kirk Waiblinger <53019676+kirkwaiblinger@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: rule-tester still crashes on (non-normalized) relative paths that are not inside cwd

3 participants