linting our code

[Michelle D'Souza]

I think we should make this change. It was suggested on list a while ago and it got a +1. 
http://lists.idrc.ocad.ca/pipermail/fluid-work/2014-January/009261.html

Lazy consensus says go for it. :)

Michelle




On 2014-03-07, at 1:00 PM, Justin Obara <obara.justin at gmail.com> 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. 
> 
> Thanks
> Justin
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20140307/009bf93d/attachment.html>