Skip to content
This repository has been archived by the owner on Mar 8, 2021. It is now read-only.

no-var rule is going to affect adoption of es6 #40

Open
chrisirhc opened this issue Sep 17, 2015 · 5 comments
Open

no-var rule is going to affect adoption of es6 #40

chrisirhc opened this issue Sep 17, 2015 · 5 comments

Comments

@chrisirhc
Copy link

Since var is everywhere in the current pre-es6 codebase, transitioning over to es6 would mean rewriting every variable declaration in the codebase to pass es6 linting. Is this what we want?
@chrisirhc chrisirhc changed the title no-vars is going to affect adoption of es6 no-var rule is going to affect adoption of es6 Sep 17, 2015
@Raynos
Copy link

Raynos commented Sep 17, 2015

It's a trivial refactor using sed

@chrisirhc
Copy link
Author

Not if you're relying on var scoping.

@Raynos
Copy link

Raynos commented Sep 18, 2015

Oh. Ugh.. :(

@chrisirhc
Copy link
Author

I'll ponder about this more, maybe it'll end up being an easy sed. Just wanted to put this up for comment/thoughts.

@lxe
Copy link

lxe commented Sep 19, 2015

Why no --es6 flag for linting es6 code?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chrisirhc @Raynos @lxe