Created
April 8, 2010 15:21
-
-
Save rwaldron/360178 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test: | |
var foo = { bar : 'barberic' | |
, baz : 'bazterd' | |
, duck : 'punch' | |
}; | |
JSLint Results: | |
Error: | |
Problem at line 1 character 19: Bad line breaking before ','. | |
var foo = { bar : 'barberic' | |
Problem at line 2 character 19: Bad line breaking before ','. | |
, baz : 'bazterd' |
Woosh
No... I got it. I'm just trying to take a stand against this idiotic practice. (though humor is always appreciated)
If jslint encourages a coding practice that makes errors harder to spot, then it IS broken.
Thom's original comment was spot on.
Well, JSLint does spot the missing comma issue, I guess it wants to keep it's job.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Huh? JSLint is not broken - comma-first coding is broken.