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

tools: set eslint comma-spacing to 'warn' #1672

Closed
wants to merge 1 commit into from

Conversation

silverwind
Copy link
Contributor

eslint takes comment as whitespace, resulting in code like

[0x2E/*'.'*/, 0x2B/*'+'*/, 0x2D/*'-'*/]

failing the linter. This change reduces the comma-spacing rule to a warning, making make lint pass. I also fixed some misc whitespace issues in .eslintrc.

encountered in: #1650
eslint issue: eslint/eslint#2408

cc: @yosuke-furukawa

@yosuke-furukawa
Copy link
Member

LGTM.

silverwind added a commit that referenced this pull request May 11, 2015
Certain cases with comments inside arrays or object literals fail to
pass eslint's comma-spacing rule. This change sets the comma-spacing
rule to the 'warn' level.

Once eslint/eslint#2408 is resolved and
released, this rule should be set back to 'error' level.

PR-URL: #1672
Reviewed-By: Yosuke Furukawa <[email protected]>
@silverwind
Copy link
Contributor Author

Thanks, landed in f07b3b6. Also added a note to the commit message to restore the rule to error level once the root issue is resolved.

@silverwind silverwind closed this May 11, 2015
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request May 19, 2015
Certain cases with comments inside arrays or object literals fail to
pass eslint's comma-spacing rule. This change sets the comma-spacing
rule to the 'warn' level.

Once eslint/eslint#2408 is resolved and
released, this rule should be set back to 'error' level.

PR-URL: nodejs#1672
Reviewed-By: Yosuke Furukawa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants