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

es6 environment #1864

Closed
aeosynth opened this Issue Feb 22, 2015 · 7 comments

Comments

Projects
None yet
3 participants
@aeosynth

aeosynth commented Feb 22, 2015

i'd like an es6 environment option which enables all of the es6 rules, similar to jshint's esnext rule. to be future proof, this could take an argument specifying the exact ecmascript version.

@nzakas

This comment has been minimized.

Show comment
Hide comment
@nzakas

nzakas Feb 22, 2015

Member

It's too early to know if this is a good idea or not. We only have two es6 specific rules, and like the rest of our rules, there's no guarantee that those or any future rules make sense as defaults.

We are adding the ability to create custom environments in plugins. When that's ready, you'll be able to make your own.

Member

nzakas commented Feb 22, 2015

It's too early to know if this is a good idea or not. We only have two es6 specific rules, and like the rest of our rules, there's no guarantee that those or any future rules make sense as defaults.

We are adding the ability to create custom environments in plugins. When that's ready, you'll be able to make your own.

@nzakas nzakas closed this Feb 22, 2015

@aeosynth

This comment has been minimized.

Show comment
Hide comment
@aeosynth

aeosynth Feb 22, 2015

sorry, i meant the language options, of which there are 19? pertaining to es6.

aeosynth commented Feb 22, 2015

sorry, i meant the language options, of which there are 19? pertaining to es6.

@nzakas nzakas reopened this Feb 22, 2015

@nzakas

This comment has been minimized.

Show comment
Hide comment
@nzakas

nzakas Feb 22, 2015

Member

Ah okay. Yes, we will most likely do this once we support all of ES6.

Member

nzakas commented Feb 22, 2015

Ah okay. Yes, we will most likely do this once we support all of ES6.

@nzakas nzakas added this to the v1.0.0 milestone Feb 22, 2015

@glenjamin

This comment has been minimized.

Show comment
Hide comment
@glenjamin

glenjamin Feb 24, 2015

Contributor

I'd also like some way to mark either files or extensions as being in "es6" mode, rather than the all-or-nothing approach available currently.

Contributor

glenjamin commented Feb 24, 2015

I'd also like some way to mark either files or extensions as being in "es6" mode, rather than the all-or-nothing approach available currently.

@nzakas

This comment has been minimized.

Show comment
Hide comment
@nzakas

nzakas Feb 25, 2015

Member

Once we have an es6 environment, you'll be able to use /*eslint-env */ in a file to use it. We don't plan on supporting configuration based on file extension.

Member

nzakas commented Feb 25, 2015

Once we have an es6 environment, you'll be able to use /*eslint-env */ in a file to use it. We don't plan on supporting configuration based on file extension.

@glenjamin

This comment has been minimized.

Show comment
Hide comment
@glenjamin

glenjamin Feb 25, 2015

Contributor

Do you plan to provide a way to say which es6 features?

My main use-case is when using Babel for react files, I'd like to get the linting to use the same set of features as whatever my transform supports ideally.

Contributor

glenjamin commented Feb 25, 2015

Do you plan to provide a way to say which es6 features?

My main use-case is when using Babel for react files, I'd like to get the linting to use the same set of features as whatever my transform supports ideally.

@nzakas

This comment has been minimized.

Show comment
Hide comment
@nzakas

nzakas Feb 25, 2015

Member

@glenjamin please see http://eslint.org/docs/configuring/#specifying-language-options. Also, please send any follow-up questions to the mailing list so we can keep this issue on track.

Member

nzakas commented Feb 25, 2015

@glenjamin please see http://eslint.org/docs/configuring/#specifying-language-options. Also, please send any follow-up questions to the mailing list so we can keep this issue on track.

@nzakas nzakas removed this from the v1.0.0 milestone Mar 7, 2015

@nzakas nzakas closed this in 5fd2c11 Mar 7, 2015

@eslint eslint bot locked and limited conversation to collaborators Feb 7, 2018

@eslint eslint bot added the archived due to age label Feb 7, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.