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

no-restricted-properties is in the wrong category #7112

Closed
ljharb opened this issue Sep 10, 2016 · 2 comments · Fixed by #7118
Closed

no-restricted-properties is in the wrong category #7112

ljharb opened this issue Sep 10, 2016 · 2 comments · Fixed by #7118
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation good first issue Good for people who haven't worked on ESLint before help wanted The team would welcome a contribution from the community for this issue

Comments

@ljharb
Copy link
Sponsor Contributor

ljharb commented Sep 10, 2016

https://github.com/eslint/eslint/blob/master/lib/rules/no-restricted-properties.js#L18 is in http://eslint.org/docs/rules/#nodejs-and-commonjs and I'm not sure why - this is a generic rule and has nothing to do with node and commonJS. It seems like "best practices" or "stylistic" is a better category for it?

@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Sep 10, 2016
@kaicataldo kaicataldo added bug ESLint is working incorrectly documentation Relates to ESLint's documentation evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion accepted There is consensus among the team that this change meets the criteria for inclusion and removed triage An ESLint team member will look at this issue soon evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion labels Sep 10, 2016
@kaicataldo
Copy link
Member

I agree! My vote is for "Best Practices":

These rules relate to better ways of doing things to help you avoid problems

@kaicataldo kaicataldo added good first issue Good for people who haven't worked on ESLint before help wanted The team would welcome a contribution from the community for this issue labels Sep 10, 2016
alecharmon pushed a commit to alecharmon/eslint that referenced this issue Sep 11, 2016
alecharmon pushed a commit to alecharmon/eslint that referenced this issue Sep 11, 2016
@kaicataldo kaicataldo removed the bug ESLint is working incorrectly label Sep 11, 2016
@kaicataldo
Copy link
Member

Removing the bug label so it's clear this is a docs change. Sorry for the confusion!

alecharmon pushed a commit to alecharmon/eslint that referenced this issue Sep 12, 2016
jaylaw81 pushed a commit to appirio-digital/ads-best-practices that referenced this issue Sep 19, 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
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation good first issue Good for people who haven't worked on ESLint before help wanted The team would welcome a contribution from the community for this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants