Roadmap: 2.0.0

[nzakas]

This issue is a tracking issue so we can more easily see what we're working towards for ESLint v2.0.0. These tasks won't necessarily wait for 2.0.0, but rather, we will know it's time for 2.0.0 once the non-breaking items in this list are complete. At that point, we can start working on the breaking changes and prepare for 2.0.0. For context on many of these, see #2203.

These are not in priority order:

• Autofixing certain errors (lead: @nzakas, Implement autofixing #3134)
• Autocreate configuration based on code sample (lead: @IanVS Autocreate configuration from existing project code #3567)
• Suffixed .eslintrc files (lead: @nzakas, Request: support .eslint.yaml as a valid config filename #4045)
• Code path analysis (lead: @mysticatea, Proposal: Code Path Analysis! [$50] #3530)
• Breaking: Treat package.json like .eslintrc (lead: @nzakas, Treat package.json just like .eslintrc files #4451)
• Breaking: Update eslint:recommended rules list (lead: ?)
• Breaking: Create yield-star-spacing (lead: ?, Create yield-star-spacing rule #4115)
• Breaking: Move ES6 globals from builtin to es6 environment (lead: @nzakas, no-undef does not catch Promise #4085)
• Breaking: Cleaner JSON Schemas for rules (lead: @btmills , Proposal: Cleaner JSON Schemas #3625)
• Breaking: Make .eslintignore work exactly like .gitignore (lead: @JulianLaval, Make .eslintignore work like .gitignore [$100] #2365)
• Breaking: Ignore bower_components by default (lead: @JulianLaval, Ignoring bower_components by default #3550)

This issue will be closed when all of the subissues are complete. We may add more into this list as needed.

[btmills]

I can take lead on cleaner schemas for #3625.

[nzakas]

Great, updated the description

[platinumazure]

What sort of approach should be taken for updating the eslint:recommended list?

[nzakas]

We just need to see if there are any other rules that should be on by default to avoid possible errors.

[puzrin]

I've tried 2.0beta2 on my projects. Everything looks nice except one too restrictive behaviour in indent rule #5073. It would be nice if it could be fixed for 2.0 (or, at least, not frozen to 3.0)

[nzakas]

Looks like we've cleared the board for 2.0.0, so closing.

[CrabDude]

It seems all roads end here for "glob matching" / "config by file extension" / --ext in config.

Where has this (previously on the roadmap) feature gone?* (Solely seeking information)
Are there any (post-2.0.0) open/tracking issues or discussions on glob-matching/file-ext config?

See #2203 (comment), #2274 (comment), #2473 (comment), #2565 (comment), #2958 (comment), #3105 (comment), #3105 (comment)
CC @lo1tuma, @ilyavolodin, @btmills,

[IanVS]

@CrabDude the tracking issue is: #3611