Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: JAVASCRIPT-1.0
-
Component/s: JavaScript
-
Labels:None
-
Number of attachments :
Description
JSLint should be fully replaced by own rule engine (SONARPLUGINS-1788).
And here is some reasons to not use JSLint:
- Almost always stops execution before reporting all violations - jslint-stopping-error.png
. Note that this leads to side effects in project history. - Quality of rules leaves much to be desired - jslint-line-too-long.png
. - No granularity of rules and thus no control via profile - jslint-other-rules.png
. - Size of dependencies - around 1 MB.
Issue Links
- relates to
-
SONARPLUGINS-1788
Provide JavaScript rule engine based on SSLR
-
- supercedes
-
SONARPLUGINS-1546
Misspelled property prefix
-
-
SONARPLUGINS-1670
Would like to pick either JSLint or JSHint as my code analysis tool
-
-
SONARPLUGINS-1045
Update jslint4java to version 2.0.2
-
Done.