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

Fix: sort-vars crash on mixed destructuring declarations #8245

Merged
merged 1 commit into from Mar 16, 2017

Conversation

not-an-aardvark
Copy link
Member

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

[x] Bug fix

Tell us about your environment

  • ESLint Version: master
  • Node Version: 7.7.2
  • npm Version: 4.1.2

What parser (default, Babel-ESLint, etc.) are you using?

default

Please show your full configuration:

parserOptions:
  ecmaVersion: 2015
rules:
  sort-vars: [error, { ignoreCase: true }]

What did you do? Please include the actual source code causing the issue.

var {a} = 1, b;

What did you expect to happen?

I expected ESLint to not crash.

What actually happened? Please include the actual, raw output from ESLint.

ESLint crashed.

Cannot read property 'toLowerCase' of undefined
TypeError: Cannot read property 'toLowerCase' of undefined
    at VariableDeclaration.node.declarations.reduce (/path/to/eslint/lib/rules/sort-vars.js:49:60)
    at Array.reduce (native)
    at EventEmitter.VariableDeclaration (/path/to/eslint/lib/rules/sort-vars.js:40:35)
    at emitOne (events.js:96:13)
    at EventEmitter.emit (events.js:191:7)
    at NodeEventGenerator.enterNode (/path/to/eslint/lib/util/node-event-generator.js:39:22)
    at CodePathAnalyzer.enterNode (/path/to/eslint/lib/code-path-analysis/code-path-analyzer.js:607:23)
    at CommentEventGenerator.enterNode (/path/to/eslint/lib/util/comment-event-generator.js:98:23)
    at Controller.enter (/path/to/eslint/lib/eslint.js:928:36)
    at Controller.__execute (/path/to/eslint/node_modules/estraverse/estraverse.js:397:31)

What changes did you make? (Give an overview)

By design, sort-vars ignores destructuring assignments. However, the rule previously didn't account for the case where the first declarator of a variable declaration was a destructuring assignment -- this led to a crash. This commit updates the rule to handle this case properly.

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

Nothing in particular

By design, sort-vars ignores destructuring assignments. However, the rule previously didn't account for the case where the first declarator of a variable declaration was a destructuring assignment -- this led to a crash. This commit updates the rule to handle this case properly.
@not-an-aardvark not-an-aardvark added accepted There is consensus among the team that this change meets the criteria for inclusion bug ESLint is working incorrectly rule Relates to ESLint's core rules labels Mar 14, 2017
@mention-bot
Copy link

@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nzakas, @vitorbal and @ilyavolodin to be potential reviewers.

@eslintbot
Copy link

LGTM

@not-an-aardvark not-an-aardvark merged commit 13eead9 into master Mar 16, 2017
@not-an-aardvark not-an-aardvark deleted the sort-vars-destructuring branch March 16, 2017 04:50
@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 bug ESLint is working incorrectly rule Relates to ESLint's core rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants