Skip to content

Conversation

@nayounsang
Copy link
Contributor

PR Checklist

Overview

As project is null when projectService is true, we have to fix validate logic

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @nayounsang!

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 Jun 21, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit b483190
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/6909f96ce4a3fa0008cc3099
😎 Deploy Preview https://deploy-preview-11327--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: 91 (🔴 down 5 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 Jun 21, 2025

View your CI Pipeline Execution ↗ for commit b483190

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

☁️ Nx Cloud last updated this comment at 2025-11-04 13:14:21 UTC

@nayounsang nayounsang marked this pull request as draft June 21, 2025 11:14
@nayounsang
Copy link
Contributor Author

Why tests was failed in CI?
In my local, there was no problem.

@nayounsang
Copy link
Contributor Author

nayounsang commented Jun 23, 2025

Can't reproduce test errors in local development.
In test, parseSettings.singleRun from packages/typescript-estree/src/parser.ts/parseAndGenerateServices is false.
So, it doesn't seem to be related to this commit.
I verified that the test results and (of course) the singleRun results did not change before and after the commit.
This work only affects singleRun.

@nayounsang nayounsang marked this pull request as ready for review June 23, 2025 08:07
@JoshuaKGoldberg JoshuaKGoldberg added awaiting response Issues waiting for a reply from the OP or another party and removed awaiting response Issues waiting for a reply from the OP or another party labels Jul 14, 2025
@JamesHenry JamesHenry assigned JamesHenry and unassigned JamesHenry Jul 15, 2025
@JamesHenry JamesHenry force-pushed the singlerun-true branch 2 times, most recently from fcdcb41 to de26768 Compare July 15, 2025 19:27
@JamesHenry
Copy link
Member

@JoshuaKGoldberg @nayounsang Ok this one drove me a little insane working my way to a reproduction, but it actually has nothing to do with caching, it is all to do with whether CI=true is set or not (which is why it happens only on CI and not locally by default).

In other words, you should be able to repro with:

CI=true TYPESCRIPT_ESLINT_PROJECT_SERVICE=true nx test typescript-estree --skip-nx-cache

@nayounsang
Copy link
Contributor Author

Thanks for helping us find the cause of this weird bug. Now let's fix our logic to fix the CI test failure.

@nayounsang nayounsang marked this pull request as draft July 18, 2025 11:22
@codecov
Copy link

codecov bot commented Jul 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.66%. Comparing base (5ec8c58) to head (b483190).
⚠️ Report is 176 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11327      +/-   ##
==========================================
- Coverage   90.86%   90.66%   -0.20%     
==========================================
  Files         503      518      +15     
  Lines       51028    52435    +1407     
  Branches     8418     8686     +268     
==========================================
+ Hits        46366    47541    +1175     
- Misses       4648     4880     +232     
  Partials       14       14              
Flag Coverage Δ
unittest 90.66% <100.00%> (-0.20%) ⬇️

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

Files with missing lines Coverage Δ
...escript-estree/src/parseSettings/inferSingleRun.ts 100.00% <100.00%> (ø)

... and 84 files 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.

@nayounsang
Copy link
Contributor Author

nayounsang commented Jul 19, 2025

Hi @JoshuaKGoldberg . Thank you for always helping me. I would like to ask you a question.
I want to test that singleRun works without any problems even when extraFileExtensions is set & projectService is truthy. But, I don't know how to write test scenarios and where to test them.

(I can see the processing extraFileExtensions logic in packages/typescript-estree/src/useProgramFromProjectService.ts
, but... I don't know if it's related to this issue.)

@nayounsang
Copy link
Contributor Author

nayounsang commented Jul 21, 2025

When singleRun & projectService is true and given extraFileExtensions in packages/typescript-estree/tests/lib/semanticInfo-singleRun.test.ts, check the program is generated.

const resultProgram = parseAndGenerateServices(code, options).services
        .program;
expect(resultProgram).toStrictEqual(mockProgram);

Because, the code is to solve the bug that occurs when programInstance is not found in the singleRun environment.

@nayounsang nayounsang marked this pull request as ready for review July 21, 2025 08:45
it('should create program when extraFileExtensions is provided in projectService and singleRun mode', () => {
vi.stubEnv('TSESTREE_SINGLE_RUN', 'true');

const resultProgram = parseAndGenerateServices(code, {
Copy link
Contributor Author

@nayounsang nayounsang Jul 21, 2025

Choose a reason for hiding this comment

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

As asked, I'm not sure if testing like this is desirable.
parseAndGenerateService -> getProgramAndAST (in singleRun, get AST and program) -> useProgramFromProjectService -> extraFileExtensions

Copy link
Member

Choose a reason for hiding this comment

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

Yeah I'd remove this test change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I committed

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.

The first && added seems off to me, but the other looks good. Am I reading it right?

it('should create program when extraFileExtensions is provided in projectService and singleRun mode', () => {
vi.stubEnv('TSESTREE_SINGLE_RUN', 'true');

const resultProgram = parseAndGenerateServices(code, {
Copy link
Member

Choose a reason for hiding this comment

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

Yeah I'd remove this test change.

@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Sep 3, 2025
@github-actions github-actions bot removed the awaiting response Issues waiting for a reply from the OP or another party label Sep 14, 2025
@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Sep 15, 2025
@JoshuaKGoldberg JoshuaKGoldberg self-requested a review October 27, 2025 12:47
@github-actions github-actions bot removed the awaiting response Issues waiting for a reply from the OP or another party label Oct 27, 2025
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.

Ok I think we're pretty much there - just the one logical change. 🚀

@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Nov 3, 2025
@github-actions github-actions bot removed the awaiting response Issues waiting for a reply from the OP or another party label Nov 4, 2025
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.

✨ great, thanks!

Since I was so involved with this, someone else from @typescript-eslint/triage-team should probably take a look too.

@JoshuaKGoldberg JoshuaKGoldberg added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Nov 4, 2025
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(typescript-estree): never infers singleRun as true for project service

3 participants