You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: