Put /*ignore jslint start*/ before and /*ignore jslint end*/ after the code to be ignored. Ex: function ignore(){ /*ignore jslint start*/ var x; var y; /*ignore jslint end*/ } Or export JsLint settings, define your IgnoreErrorStart/ IgnoreErrorEnd symbols and import. Edit Some folks may confuse this answer with JSHint. In that case, use these: /*jshint … Read more
As this is the top rated google hit and other people might not be seeing it at first in the jslint tool, there is a option called “Tolerate misordered definitions” that allows you to hide this type of error. /*jslint latedef:false*/
From the documentation JSLint also recognizes a /*global */ directive that can indicate to JSLint that variables used in this file were defined in other files. The comment can contain a comma separated list of names. Each name can optionally be followed by a colon and either true or false, true indicating that the variable … Read more
First of all, never use a for in loop to enumerate over an array. Never. Use good old for(var i = 0; i<arr.length; i++). The reason behind this is the following: each object in JavaScript has a special field called prototype. Everything you add to that field is going to be accessible on every object … Read more
Your code might be perfectly correct (it might also be problematic, depending on how you call testConstr). My suggestion is: tell JSLint to shut up Or don’t use JSLint at all.
JSHint says “Possible strict violation” because you are using this inside something that, as far as it can tell, is not a method. In non-strict mode, calling gotoPage(5) would bind this to the global object (window in the browser). In strict mode, this would be undefined, and you would get in trouble. Presumably, you mean … Read more
IMO, blindly using ===, without trying to understand how type conversion works doesn’t make much sense. The primary fear about the Equals operator == is that the comparison rules depending on the types compared can make the operator non-transitive, for example, if: A == B AND B == C Doesn’t really guarantees that: A == … Read more
[^\s;|\\*'”!,()<>] matches any ASCII character other than the ones listed, and any non-ASCII character. Since JavaScript strings are Unicode-aware, that means every character known to Unicode. I can see a lot of potential for mischief there. Rather than disable the warning, I would rewrite the character class to match the characters you do want to … Read more
It only will do this if you have the option selected at the bottom: Disallow insecure . and [^…] in /RegExp/ From the docs: true if . and [^…] should not be allowed in RegExp literals. These forms should not be used when validating in secure applications. So the answer your question, if you start … Read more
Move the function outside the loop: function dummy() { return this.name_; } // Or: var dummy = function() {return this.name;}; for (var i = 0; i<processorList.length; ++i) { result[i] = { processor_: timestampsToDateTime(processorList[i]), name_: processorList[i].processorName, getLabel: dummy }; } … Or just ignore the message by using the loopfunc option at the top of the … Read more