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: Ensuring eslint:recommended rules are sorted. #8106

Merged
merged 2 commits into from Feb 20, 2017

Conversation

platinumazure
Copy link
Member

Also renaming to conf/eslint-recommended.js for parity with conf/eslint-all.js and ensuring references are fixed as well.

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain: Chore: See commit summary and body above.

What changes did you make? (Give an overview)

Goal was to ensure that our eslint:recommended list is sorted alphabetically. In order to ensure that, I've converted the file to a .js, added some ESLint comments to enable sort-keys on that file (and also actually sorted the rules).

Since I needed to go through all references and fix those (require statements had to use the file extension, etc.), I figured I might as well rename the file to conf/eslint-recommended.js for greater clarity. This will allow new contributors to more easily find the

Is there anything you'd like reviewers to focus on?

Nothing in particular.

Also renaming to conf/eslint-recommended.js for parity with conf/eslint-all.js and ensuring references are fixed as well.
@eslintbot
Copy link

LGTM

@mention-bot
Copy link

@platinumazure, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nzakas, @gyandeeps and @mysticatea to be potential reviewers.

Copy link
Member

@ilyavolodin ilyavolodin left a comment

Choose a reason for hiding this comment

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

I think in a long run we should stop using json file all together, and use metadata to generate those lists at release time. But for now, this is fine, I guess.

@gyandeeps gyandeeps merged commit 21be366 into master Feb 20, 2017
@ilyavolodin ilyavolodin deleted the rename-eslint-recommended branch February 20, 2017 17:08
pantosha pushed a commit to pantosha/eslint that referenced this pull request Feb 21, 2017
* Chore: Ensuring eslint:recommended rules are sorted.

Also renaming to conf/eslint-recommended.js for parity with conf/eslint-all.js and ensuring references are fixed as well.

* Chore: Fix Makefile message for missing eslint:recommended configuration
@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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants