rules.jshint.I003.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of sonar-web-frontend-js Show documentation

Consume reports generated by jshint for code quality. Also consume reports for code duplication (either simian or cpd). Consumes the unit/integration tests reports (generated by Jasmin) coverage report (lcov generated by Istanbul). The information generated by reports are added in Sonar

There is a newer version: 2.1.0

Show newest version


    When do I get this error?
The "ES5 option is now set per default" error is thrown when JSHint (version
2.0.0 and above only) encounters the es5 option with a value of true.
Here's an example in which we set the es5 option so we can use reserved words
as property identifers (which was not allowed in ES3):
x
 
1
/*jshint es5: true */
2
var x = {
3
    default: 10
4
};
5
JSHint found no errorsWhich linter should be used for this code snippet:
 JSLint JSHint ESLint
Which version of the linter should be used:
Version 2.9.0

Why do I get this error?
This error is raised to highlight a *pointless piece of code. If you're using
JSHint 2.0.0 or above, the es5 option will be set to true by default, due to
the fact that environments supporting the ES5 spec are now far more widespread.
You can simply remove the option from any JSHint directives or .jshintrc
files. Select JSHint version 1.1.0 or below in the following example to see the
difference from when the es5 option was not on by default:
4
 
1
var x = {
2
    default: 10
3
};
4
JSHint found no errorsWhich linter should be used for this code snippet:
 JSLint JSHint ESLint
Which version of the linter should be used:
Version 2.9.0

In JSHint 1.0.0 and above you have the ability to ignore any warning with a
special option syntax. Since this is an informational JSHint
message, it cannot be disabled.