Hi
Dne Tue, 16 Apr 2013 10:51:30 +0800 adam adamgsoc2013@gmail.com napsal(a):
About the JSHint (or JSLint), there are some opintions which can be customed by users to decide whether the warning should be evoked. Like JSHint: http://www.jshint.com/ Warn
About debugging code About unsafe for..in About == null About arguments.caller and .callee About empty blocks About unsafe comparisons About assignments inside if/for/... About functions inside loops About eval About unsafe line breaks When bitwise operators are used When code is not in strict mode When variable is undefined When variable is defined but not used When blocks omit {} When new is used for side effects
If we want to fix the JSHint warning, we should firstly decide which warnings should be fixed. thanks BTW, I would like to join and fix some warnings.
Yes, that's why I'm asking here :-). The current set of warnings is mostly based on defaults, but we can either choose to tune it or to fix the warnings it reports.