Why is the esnext option ignored?

[UltCombo]

Referring to dbb347e

Sure --esnext is buggy, but I believe this plugin should not just silently ignore this option when the user requests to use it.

[gustavohenke]

Hmmm... well, maybe the commit message wasn't well formed.
We aren't really ignoring it, this array is used to distinct configurations from rules.

Suppose you have the following configuration:

jscs: {
  options: {
    requireCurlyBraces: [ "if" ],
    esnext: true
  },
  src: ".."
}

This way, the requireCurlyBraces is passed as a rule for JSCS while esnext is recognized as an configurable option of JSCS, so no Unsupported rule: foo will happen.

[UltCombo]

Ohh my bad. Let me run another test to see.

[gustavohenke]

If you still find it's buggy or is being really ignored, let me know!

[UltCombo]

@gustavohenke looks like I'm still having issues. I'll try to prepare an isolated test case. =]

[UltCombo]

@gustavohenke here's a test case:

• Clone https://github.com/UltCombo/grunt-jscs-62
• cd into the directory
• Run jscs --esnext index.js (must have jscs globally installed) -- works fine.
• Run grunt -- fails with "Unexpected reserved word". I believe the Gruntfile is correct, isn't it?

[gustavohenke]

It's everything okay with your example.
Seems like we messed up stuff in the latest release.

I'm patching grunt-jscs right now!

[UltCombo]

Thanks for the quick response. 😃

[gustavohenke]

Fix landed in v0.8.1!

[UltCombo]

Thank you very much! :D