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

[eslint config] [breaking] enable quote-props rule. #632

Merged
merged 1 commit into from
Jan 4, 2016

Conversation

ljharb
Copy link
Collaborator

@ljharb ljharb commented Dec 22, 2015

This is the rule we follow at Airbnb, but the styleguide and linter plugin haven't been enforcing it.

@ljharb ljharb mentioned this pull request Dec 23, 2015
@ljharb ljharb force-pushed the ljharb/quote_props branch 5 times, most recently from 6d479cb to 1ab2f02 Compare December 24, 2015 22:23
@ljharb ljharb force-pushed the ljharb/quote_props branch 7 times, most recently from 960506e to 4cdc3fe Compare January 4, 2016 19:38
ljharb added a commit that referenced this pull request Jan 4, 2016
[eslint config] [breaking] enable `quote-props` rule.
@ljharb ljharb merged commit 77eda9a into master Jan 4, 2016
@ljharb ljharb deleted the ljharb/quote_props branch January 4, 2016 21:36
@@ -85,7 +85,8 @@ module.exports = {
// enforce padding within blocks
'padded-blocks': [2, 'never'],
// require quotes around object literal property names
'quote-props': 0,
// http://eslint.org/docs/rules/quote-props.html
'quote-props': [2, 'as-needed', { 'keywords': true, 'unnecessary': true, 'numbers': false }],

Choose a reason for hiding this comment

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

what about 'new' keyword ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Since we recommend using babel, which takes care of quoting reserved property names in legacy engines, this is not a concern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants