Skip to content

fix(parser): error when both projectService and project are set #11333

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MariaSolOs
Copy link
Contributor

@MariaSolOs MariaSolOs commented Jun 23, 2025

PR Checklist

Overview

As mentioned in the issue, the docs aren't clear of what the parser will use when both projectService and project are set. When such case is detected, I think it's better to be explicit about the misconfiguration and error as early as possible.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @MariaSolOs!

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.

Copy link

netlify bot commented Jun 23, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 63d37d4
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/68a7c5bbd79c6c0008de9530
😎 Deploy Preview https://deploy-preview-11333--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: 98 (🟢 up 4 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.

Copy link

nx-cloud bot commented Jun 23, 2025

View your CI Pipeline Execution ↗ for commit 63d37d4

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

☁️ Nx Cloud last updated this comment at 2025-08-22 01:30:27 UTC

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.

These are just notes from quick preliminary review. I think we have a good path forward but should definitely let other team folks weigh in in #11319.

For now, I'll switch this PR to draft so it doesn't show up on the queue. But we can definitely un-draft it once the issue's discussion is done.

@JoshuaKGoldberg JoshuaKGoldberg marked this pull request as draft June 30, 2025 20:02
@MariaSolOs
Copy link
Contributor Author

@JoshuaKGoldberg Thanks for the review! I'll wait for further thoughts from other maintainers before I continue working on this :)

@MariaSolOs MariaSolOs marked this pull request as ready for review August 22, 2025 01:04
Copy link

codecov bot commented Aug 22, 2025

Codecov Report

❌ Patch coverage is 55.55556% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.87%. Comparing base (369ccab) to head (63d37d4).

Files with missing lines Patch % Lines
...pt-estree/src/parseSettings/createParseSettings.ts 55.55% 4 Missing ⚠️

❌ Your patch check has failed because the patch coverage (55.55%) 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   #11333      +/-   ##
==========================================
- Coverage   90.87%   90.87%   -0.01%     
==========================================
  Files         505      505              
  Lines       51146    51155       +9     
  Branches     8424     8428       +4     
==========================================
+ Hits        46480    46485       +5     
- Misses       4652     4656       +4     
  Partials       14       14              
Flag Coverage Δ
unittest 90.87% <55.55%> (-0.01%) ⬇️

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

Files with missing lines Coverage Δ
...pt-estree/src/parseSettings/createParseSettings.ts 91.22% <55.55%> (-1.47%) ⬇️
🚀 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.

@@ -19,6 +19,7 @@ env:
NX_CLOUD_ACCESS_TOKEN: ${{ secrets.NX_CLOUD_ACCESS_TOKEN }}
# This increases the verbosity of the logs for everything, including Nx Cloud, but will hopefully surface more info about recent lint failures
NX_VERBOSE_LOGGING: false
TYPESCRIPT_ESLINT_IGNORE_PROJECT_AND_PROJECT_SERVICE_ERROR: true
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 tried setting this variable here but it was undefined when running the tests on CI 🤷🏻‍♀️

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The problem of setting it here is that then I'm not able to write a test that hits the new error codepath, and so that's why the coverage check is screaming at me.

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