On Jan 14, 7:12 pm, cancel bubble <cancelbub...@gmail.com> wrote: > At jslint.com (which I use from time to time depending on where I'm working) > with no apparent checkbox option to disable this test. > > Can you all help me out and let me know why this is a good idea? > > Part of my job is supporting existing apps that utilize A LOT of JS (some > legacy) and some of these files are thousands of lines. I can no longer > jslint these files because I get a critical error at say, line 50 (the first > occurence of a var not at the top of a func). If I were to fix that, I > would just get another one at line 93. Then 140. Repeat ad nauseum. I'm > not going to go through an fix these in huge files, I will just stop linting > them because I'm not going to get any support for regression testing. > > Why is this not an optional test? I'm looking for an answer other than > "because Crockford says so and I'm swinging from his nuts." > > I understand that it's good practice to declare all your vars at the top of > your function, what I don't understand is why you can't toggle this check > when you're dealing with old, large code. You can't get past the first > error this trips up unless you edit your code (which works just fine).
Have you tried "http://www.javascriptlint.com"; instead ? It is a good alternative Javascript Lint tool. That may give you a little more freedom in specifying different options or just turn them off. It seems more configurable to me and I have used it continuously in my projects. If you are serious about the code quality you should always run a lint tool. -- Diego -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/jsmentors@jsmentors.com/ To search via a non-Google archive, visit here: http://www.mail-archive.com/jsmentors@googlegroups.com/ To unsubscribe from this group, send email to jsmentors+unsubscr...@googlegroups.com
