I personally am a little hesitant to have to follow a certain coding style + am worried about outside contributors struggling with it. On the other hand, it would be nice for code readability to have uniform/consistent style.
As long as we discuss what styles we want to use beforehand, I am open to it. On Thu, Jul 31, 2014 at 7:34 PM, Mark Koudritsky <[email protected]> wrote: > Just opened a pull request with an experimental JSCS config. Would be glad > to get some feedback about this. My goal is to eventually run JSCS together > with JSHint as part of `npm test`. This is a relatively liberal config that > doesn't generate too many warnings with the existing code. > > https://github.com/apache/cordova-lib/pull/69 > > > ## Some background > > JSHint people want to focus on syntax linting and are dropping style > oriented > options. They recommend using JSCS (in addition to JSHint) for style: > https://github.com/jshint/jshint/issues/1339 > > Options dropped from JSHint were added to JSCS some time ago: > https://github.com/mdevils/node-jscs/issues/102 > > I'm using it with SublimeLinter-jscs > https://sublime.wbond.net/packages/SublimeLinter-jscs >
