Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

not-an-aardvark
Copy link
Member

@not-an-aardvark not-an-aardvark commented Aug 26, 2017

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?

@not-an-aardvark not-an-aardvark added chore This change is not user-facing evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion labels Aug 26, 2017
@eslintbot
Copy link

LGTM

@mention-bot
Copy link

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

@gyandeeps
Copy link
Member

Can we move .eslintplugin.js file to folder rather than polluting the base folder with so many files?

@not-an-aardvark
Copy link
Member Author

not-an-aardvark commented Aug 26, 2017

No, unfortunately not. eslint-plugin-local just consists of module.exports = require('../../.eslintplugin'), so with this solution we would need to have .eslintplugin.js in the root directory.

@eslintbot
Copy link

LGTM

@eslintbot
Copy link

LGTM

@eslintbot
Copy link

LGTM

@eslintbot
Copy link

LGTM

@not-an-aardvark
Copy link
Member Author

not-an-aardvark commented Oct 16, 2017

@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 --rulesdir), and they would help us dogfood the recommended approaches for project-specific linting rules.

edit: fixed incorrect PR link

@aladdin-add
Copy link
Member

aladdin-add commented Oct 16, 2017

I'm slightly prefer that one (#9164), as .eslintplugin.js file in the root dir in this PR.

@not-an-aardvark
Copy link
Member Author

I'm slightly prefer that one (#9163)

Did you mean to link to #9164 instead of #9163? #9163 is this PR.

@aladdin-add
Copy link
Member

aladdin-add commented Oct 16, 2017

yes~(⌒▽⌒)

it's because the PR you mentioned:

@eslint/eslint-team Any thoughts on this PR or #9163?

@not-an-aardvark
Copy link
Member Author

Closing because #9164 was merged.

@not-an-aardvark not-an-aardvark deleted the use-eslint-plugin-local branch October 28, 2017 08:43
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Apr 27, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Apr 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants