Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(eslint-plugin): refactor lint script to run all projects without running eslint-plugin separately #8779

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

Closed
wants to merge 2 commits into from

Conversation

abarghoud
Copy link

@abarghoud abarghoud commented Mar 26, 2024

PR Checklist

Overview

The current lint script sequence includes a direct linting command followed by additional linting tasks executed through NX CLI. However, this approach has led to unintended consequences due to how Yarn forwards arguments at the end of the called script, particularly when attempting to pass options such as --fix.

By removing the direct linting command and focusing solely on executing linting tasks through NX CLI, we can avoid the issue altogether. This simplification streamlines the script and eliminates potential conflicts arising from Yarn's argument forwarding behavior.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @abarghoud!

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 Mar 26, 2024

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit f18bfae
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/6605bddd76200c0008220d5e
😎 Deploy Preview https://deploy-preview-8779--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
Accessibility: 100
Best Practices: 92
SEO: 98
PWA: 80
View the detailed breakdown and full score reports

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

Copy link

nx-cloud bot commented Mar 26, 2024

@abarghoud abarghoud changed the title fix(8733): Refactor lint script to run all projects without running eslint-plugin separately fix(repo): Refactor lint script to run all projects without running eslint-plugin separately Mar 26, 2024
@abarghoud abarghoud changed the title fix(repo): Refactor lint script to run all projects without running eslint-plugin separately chore: Refactor lint script to run all projects without running eslint-plugin separately Mar 26, 2024
@abarghoud abarghoud changed the title chore: Refactor lint script to run all projects without running eslint-plugin separately fix(eslint-plugin): Refactor lint script to run all projects without running eslint-plugin separately Mar 26, 2024
@abarghoud abarghoud changed the title fix(eslint-plugin): Refactor lint script to run all projects without running eslint-plugin separately fix(eslint-plugin): refactor lint script to run all projects without running eslint-plugin separately Mar 26, 2024
@abrahamguo
Copy link
Contributor

abrahamguo commented Mar 27, 2024

@abarghoud Have you looked at @JamesHenry's PR #8539 where linting eslint-plugin was broken out, to ensure that you are not introducing regressions?

#8373 as well

@abarghoud
Copy link
Author

@abarghoud Have you looked at @JamesHenry's PR #8539 where linting eslint-plugin was broken out, to ensure that you are not introducing regressions?

#8373 as well

@abrahamguo Thank you for bringing up PR #8539 and issue #8373. I've reviewed both and understand the context behind breaking out linting for eslint-plugin. It appears that the flakiness issues observed in those PRs were specific to the CI environment. My PR has passed all CI checks, including linting, which assures that it's aligned with project standards and hasn't introduced regressions.

According to what @JoshuaKGoldberg said in #8373 description

These all work locally for me. Maybe it's an out-of-memory issue in CI or something along those lines?

Is there any way I can reproduce the flakiness that was happening?

@bradzacher bradzacher added the bug Something isn't working label Apr 4, 2024
@abarghoud abarghoud closed this May 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug(repo): yarn lint-fix in this repository doesn't work on the eslint-plugin package
3 participants