Closed mcandre closed 9 years ago
My apologies, but again, this is a Crockford-ism which would need to be addressed upstream and in my experience, is unlikely to change.
I respect that JSLint is designed to emphasize this rule, but I don't want to hide other warnings just because this one is triggered.
As a developer, JSLint is just one of many linters I throw at my codebase; I want to see every possible check they might make, and implement the suggested code changes or turn off the rule as I prefer.
A boolean option to explicitly enable/disable stopping scanning would be much appreciated.
This is not under our control.
If at all possible, please continue scanning the rest of my code, even when encountering
Move 'var' declarations to the top of the function.