I think it’s a great idea. Let’s do it. In case it is helpful, here are some links to how I’ve configured JSHint in Flocking, which is a close relative of Infusion in many ways:
I use a .jshintrc file that contains all the options that should be used when JSHinting the repository: https://github.com/colinbdclark/Flocking/blob/master/.jshintrc I used the grunt-jshint plugin to set up a task for it so that I can lint everything by running “grunt jshint:” https://github.com/colinbdclark/Flocking/blob/master/Gruntfile.js#L7-L12 And I’m using the grunt-githook plugin to register a git pre commit hook that runs the linting every time I try to commit code: https://github.com/colinbdclark/Flocking/blob/master/Gruntfile.js#L93-L97 Colin On Mar 7, 2014, at 1:00 PM, Justin Obara <[email protected]> wrote: > For several years, we've been hosting a forked version of the > http://jslint.com at http://swarm.fluidproject.org/jslint/ . We did this so > that we could remove some of the more aggressive linting requirements while > maintaining our high code quality standards. Recently our swarm server was > taken down, and along went our forked version of JSLint. However, in the time > since we put up our version of JSLint, JSHint has grown quite a bit and can > even be run as a node module. Perhaps now is the time to make the switch to > JSHint. > > If we do make the switch we'll need to update our lint comments in each JS > file and should consider adding JSHint to our grunt build scripts. > > Please let me know what you think. _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
