Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: clean up ESLint config postvitest migration#11135

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

aryaemami59
Copy link
Contributor

PR Checklist

Overview

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@aryaemami59!

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 onhttps://opencollective.com/typescript-eslint.

@netlifyNetlify
Copy link

netlifybot commentedMay 5, 2025
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commit1551966
🔍 Latest deploy loghttps://app.netlify.com/projects/typescript-eslint/deploys/6825fffa27af400008951b63
😎 Deploy Previewhttps://deploy-preview-11135--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 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 98 (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 yourNetlify project configuration.

@nx-cloudNx Cloud
Copy link

nx-cloudbot commentedMay 5, 2025
edited
Loading

View yourCI Pipeline Execution ↗ for commit1551966.

CommandStatusDurationResult
nx test eslint-plugin✅ Succeeded6m 24sView ↗
nx run eslint-plugin:test -- --coverage✅ Succeeded6m 38sView ↗
nx test eslint-plugin --coverage=false✅ Succeeded5m 19sView ↗
nx test type-utils✅ Succeeded24sView ↗
nx test eslint-plugin-internal✅ Succeeded11sView ↗
nx test visitor-keys✅ Succeeded3sView ↗
nx run types:build✅ Succeeded1sView ↗
nx test typescript-eslint✅ Succeeded5sView ↗
Additional runs (26)✅ Succeeded...View ↗

☁️Nx Cloud last updated this comment at2025-05-15 15:08:44 UTC

@aryaemami59aryaemami59 marked this pull request as ready for reviewMay 5, 2025 10:29
@codecovCodecov
Copy link

codecovbot commentedMay 7, 2025
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.92%. Comparing base(af077a0) to head(1551966).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@##             main   #11135   +/-   ##=======================================  Coverage   90.92%   90.92%           =======================================  Files         499      499             Lines       50845    50845             Branches     8384     8384           =======================================  Hits        46231    46231             Misses       4599     4599             Partials       15       15
FlagCoverage Δ
unittest90.92% <ø> (ø)

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

🚀 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.

Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Thanks!

@JoshuaKGoldbergJoshuaKGoldberg added the 1 approval>=1 team member has approved this PR; we're now leaving it open for more reviews before we merge labelMay 12, 2025
@JoshuaKGoldbergJoshuaKGoldberg merged commitff2a785 intotypescript-eslint:mainMay 16, 2025
59 checks passed
@JamesHenry
Copy link
Member

nx config wise this is a very confusing change tbh.

Please can you share your reasoning?

@aryaemami59
Copy link
ContributorAuthor

@JamesHenry why is it confusing? Or rather which part is confusing? I'm more than happy to elaborate.

@JamesHenry
Copy link
Member

  • Why did you add the eslint plugin here? Only to then immediately remove it again herechore: update some package scripts and dependency config #10765
  • Executors and inferred plugins are two different approaches to the same problem, in this PR you are simultaneously increasing the usage of both
  • Why are you specifying that all usage of a specific executor depends upon specific tasks ("@nx/eslint:lint": { "dependsOn": ["eslint-plugin-internal:build", "typescript-eslint:build"]), that is a very unusual thing to do, and I don't think it's accurate here

The mixed usage and application and then seeming upcoming undoing of things is why I wanted to understand the broader reasoning here.

I think it's best if a publish a video on these concepts to bring us on the same page

@aryaemami59
Copy link
ContributorAuthor

aryaemami59 commentedMay 16, 2025
edited
Loading

@JamesHenry

That was actually done by mistake I just fixed it.

Comment on lines +32 to +38
},
{
"plugin": "@nx/eslint/plugin",
"include": ["packages/*"],
"options": {
"targetName": "lint"
}
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Comment on lines +92 to +101
"@nx/eslint:lint": {
"dependsOn": ["eslint-plugin-internal:build", "typescript-eslint:build"],
"options": {
"noEslintrc": true,
"cache": true,
"eslintConfig": "{workspaceRoot}/eslint.config.mjs"
},
"outputs": ["{options.outputFile}"],
"cache": true
},
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Without thisrepo:lint would not be cached unless We explicitly pass this configuration to the rootproject.json file.

"eslint-plugin-internal:build",
"typescript-eslint:build"
],
"dependsOn": ["eslint-plugin-internal:build", "typescript-eslint:build"],
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

We are only usingtypescript-eslint andeslint-plugin-internal inside theeslint.config.mjs file, thereforeeslint-plugin:build is not needed here.

@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsMay 24, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@JoshuaKGoldbergJoshuaKGoldbergJoshuaKGoldberg approved these changes

Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Repo: clean upeslint.config.mjs postvitest migration
3 participants
@aryaemami59@JamesHenry@JoshuaKGoldberg

[8]ページ先頭

©2009-2025 Movatter.jp