Timo Tijhof cf7f2b141d Set up node-jscs, pass it, and configure in local Gruntfile ... Let's experiment with this via our local Gruntfile. If it works fine we can install it in Jenkins (similar to node-csslint). Verify through $ npm install && npm test; Fixed all outstanding violations. Also: * Added syntaxhighight to ignore. * Added imetests (which contain unformatted JSON) to ignore. * In ve.dm.ModelRegistry#matchTypeRegExps, removed redundant !! cast from the [+!!withFunc] statement which was hitting a bug in node-jscs. All callers to this local private function pass a literal boolean true/false so no need to cast it. * Removed "/* key .. , value */" from ve.setProp, though this wasn't caught by node-jscs, found it when searching for " , ". * Made npm.devDependencies fixed instead of using tilde-ranges. This too often leads to strange bugs or sudden changes. Fixed them at the version they were currently ranging to. Bug: 54218 Change-Id: Ib2630806f3946874c8b01e58cf171df83a28da29		2013-12-06 10:37:27 -08:00
..
helpers	Set up node-jscs, pass it, and configure in local Gruntfile	2013-12-06 10:37:27 -08:00
rules	Expand highlighting support for syntaxhighlight module	2013-10-17 22:42:52 -04:00
styles	Fix icon opacities	2013-11-22 13:47:20 +00:00
ve.ce.MWSyntaxHighlightNode.js	Rename this.$ to this.$element, and this.$$ to this.$	2013-11-03 23:03:49 -08:00
ve.dm.MWSyntaxHighlightNode.js	Remove ve.{inheritClass,mixinClass} and use OO instead	2013-10-18 18:58:08 +02:00
ve.ui.MWSyntaxHighlightDialog.js	Window refactor	2013-11-08 12:33:25 -08:00
ve.ui.MWSyntaxHighlightSimpleSurface.js	Force LTR direction in MWSyntaxHighlightDialog	2013-11-08 13:00:39 -08:00
ve.ui.MWSyntaxHighlightTool.js	Detangle triggers from OOUI	2013-10-29 05:50:30 +00:00