1. Hinting globals for JSLint
You can also use JSLint global hints per source file to hint what globals the file has available, so JSLint won’t complain.
For example, to hint that global krusovice namespace is available, add the following line to the beginning of the file:
Note that not having wrapping spaces is important here.
2. Common warnings to ignore
JSLint is very accurate with every detail – like a Finnish-Swedish lady when it comes to cleaning your apartment. You probably don’t want to see red marker all over you code, so you might want to tune down warnings a bit.
Don’t complain about missing jQuery or Console:
.*'(\$|jQuery)' is not defined.*
.*'console' is not defined.*
3. Using sane tab setting and fixing mixed spaces and tabs
You probably want also to fix those “Mixed tabs and spaces” errors. Use AnyEdit plug-in for Eclipse to convert tabs to spaces in the selected file (see Installation section).
First you need to set sane tab site for AnyEdit, which defaults to 2 spaces (looks like you can nbe even more f*ed up as stated above). You need to fix this in Settings -> General -> Editor -> AnyEdit tools -> Convert. Set Eclipse default, 4, there.
Then select all text in the editor, right click -> Convert tabs to spaces.
What is missing
I could not find a way to ignore files. This is very irritating if you have something like jQuery UI in your source tree and you cannot supress warnings for the problematic files. Ignore regular expressions patterns don’t seem to match path or file part of the error.
Subscribe to RSS feed Follow me on Twitter Follow me on Facebook Follow me Google+