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

Possible to add a feature to enable all rules across plugins? #8079

Closed
mockdeep opened this issue Feb 14, 2017 · 3 comments
Closed

Possible to add a feature to enable all rules across plugins? #8079

mockdeep opened this issue Feb 14, 2017 · 3 comments
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion core Relates to ESLint's core APIs and features evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion feature This change adds a new feature to ESLint

Comments

@mockdeep
Copy link
Contributor

Tell us about your environment

  • ESLint Version: 3.14.1
  • Node Version: 6.8.0
  • npm Version: 4.1.2

We got the eslint:all configuration merged, but one side effect seems to be there is a trickle down effect of similar arguments happening on various ESlint plugins. One thing that might be nice, both for me as a user and for various maintainers not to have to implement this same functionality over and over, is if eslint:all or some other configuration also included all of the rules from plugins as well. Does this seem like something that is reasonable and doable? I'd be happy to take a look if people are amenable and I can get a push in the right direction.

@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Feb 14, 2017
@not-an-aardvark not-an-aardvark added core Relates to ESLint's core APIs and features evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion feature This change adds a new feature to ESLint and removed triage An ESLint team member will look at this issue soon labels Feb 15, 2017
@not-an-aardvark
Copy link
Member

Thanks for the feature request. I think I'm 👎 on this feature due to the reasons listed here. However, let's see what the rest of the team thinks.

@mockdeep
Copy link
Contributor Author

@not-an-aardvark I actually argue a lot of that here. For me I don't really care if rules are compatible or not, or whether they are considered a best practice or not. I'm still up for making my own decisions on these things, I just want a streamlined process for integrating new rules into my application.

@alberto
Copy link
Member

alberto commented Mar 11, 2017

Thanks for your interest in improving eslint. Unfortunately, it looks like this issue didn't get enough support from the team and so I'm closing it. While we wish we'd be able to accommodate everyone's requests, we do need to prioritize. We've found that issues failing to reach consensus after 21 days tend to never do it, and as such, we close those issues. This doesn't mean the idea isn't interesting, just that it's not something the team can commit to.

@alberto alberto closed this as completed Mar 11, 2017
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 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 Feb 6, 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 core Relates to ESLint's core APIs and features evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion feature This change adds a new feature to ESLint
Projects
None yet
Development

No branches or pull requests

4 participants