Project: aptanastudio
Issue APSTUD-4129: Behavior of JSLint validator options does not match those from JSLint.com
JSLint supports the addition of comments to the top of a JavaScript as a means of setting JSLint options. The comment: /\*jslint white:true\*/ instructs the validator to 'Tolerate messy white space', which more specifically should be set to 'true if strict whitespace rules should be ignored'. (Full documentation of JSLint options here: http://www.jslint.com/lint.html#options) However, in Aptana Studio the opposite is occurring. So setting 'white' to true causes whitespace to become important, rather than be ignored as expected. I've found that others have mentioned this behavior on Stack Overflow: http://stackoverflow.com/questions/6893045/jslint-options-doesnt-seem-to-work-on-aptana-3 http://stackoverflow.com/questions/8597253/problems-with-jslint-options-in-aptana-studio-3 I've also found the same reversed logic with: 'plusplus', 'undef', 'regexp', 'nomen', and 'newcap' (and there are likely others). Other observations: - the logic for 'sub' is correct - 'continue' signals a 'Bad option' warning. - 'eqeq' errors do not seem to be caught.
Story points: 8