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

const keyword support #9

Closed
mpalmerlee opened this issue Jan 19, 2013 · 2 comments
Closed

const keyword support #9

mpalmerlee opened this issue Jan 19, 2013 · 2 comments

Comments

@mpalmerlee
Copy link

Some of my team is using the const keyword which is supported in V8/node.
https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Statements/const

Right now plato shows warnings for const declarations:
const DB_NAME = 'mydb';
Column: 1 "Expected an identifier and instead saw 'const'."
Column: 1 "Expected an assignment or function call and instead saw an expression."
Column: 6 "Missing semicolon."

Is it possible this could be recognized as valid syntax? Or possibly it already is with a commandline option like jshint?

Thanks for bulding such an awesome JavaScript static analysis tool!

@jsoverson
Copy link
Member

That is jshint's arena but should be taken care of by specifying "esnext" : true in your jshintrc file. See jshint docs

If no jshintrc is specified, default jshint options are used (as defined by jshint). There's no way to disable jshint via the command line right now, but you can in the grunt task.

@mpalmerlee
Copy link
Author

Ok, thanks for the additional information and quick reply. I'll try it out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants