-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Chore: use eslint-plugin-local instead of --rulesdir for self-linting #9163
Conversation
LGTM |
@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @vitorbal, @gajus and @nzakas to be potential reviewers. |
Can we move |
No, unfortunately not. |
LGTM |
LGTM |
b705139
to
09d8151
Compare
LGTM |
09d8151
to
cc960d0
Compare
LGTM |
@eslint/eslint-team Any thoughts on this PR or #9164? I think we should accept one of them -- they would make it easier for new contributors (since editor integrations wouldn't report issues from edit: fixed incorrect PR link |
I'm slightly prefer that one (#9164), as |
yes~(⌒▽⌒) it's because the PR you mentioned:
|
Closing because #9164 was merged. |
What is the purpose of this pull request? (put an "X" next to item)
[x] Other, please explain:
What changes did you make? (Give an overview)
This updates our internal linting build to use
eslint-plugin-local
rather than the--rulesdir
CLI flag.We've been talking about deprecating
rulesdir
for awhile, so I think it would be good for us to dogfood some of the alternatives for using project-specific linting rules.#9164 is another way of solving the same problem. This PR is mutually exclusive with #9164.
Is there anything you'd like reviewers to focus on?
We should choose between this approach and the approach in #9164. Which do you prefer?