Sorry for misinterpreting your post. I see the issue.
On Sep 6, 2011, at 2:41 PM, ScottJ wrote:
> I keep a local copy of jslint too (as part of jslint_on_rails) but that doesn't solve the problem here. The issue is that one change to jslint has caused all kinds of js sources to start failing, with no option for backward compatibility. That means I have to update jslint plus *all* my js sources as one big atomic change.
> It would be preferable to be able to update one js source file, then checkin. Update another, checkin. Etc. With dozens of js source files originally written by dozens of authors, it is a real headache to get all of them updated together.
> The reality is that I will have to disable jslint in our workflow for some time, or kludge up some way to keep multiple versions of jslint active and have each source file specify which version it is compatible with.
> Neither of those are good options.
> Bottom line: A professional tool like jslint should not change so drastically without any regard for backward compatibility. That pushes people away from it, and that is a real shame.
> --- In firstname.lastname@example.org, Kent Davidson <kent@...> wrote:
> > Scott,
> > What we do at my company is pull down versions of the jslint code and site and then host it internally on test web servers (e.g. test.example.com/jslint.com/), and then use Selenium to automatically place our JS code into it and check for errors.
Market Ruler, LLC
Marketing Power Tools
+1 866-622-8636 x88
[Non-text portions of this message have been removed]