Conversation
|
Haha - I don't TOTALLY hate this and definitely appreciate the thought behind it. The semi-colons stuff is definitely groovy. I switch back and forth between using semi-colons or not, but as my team at work has decided to use semi-colons all the way I figured I should start doing it in open source too for consistency and practice. I missed a few places though here & am thankful you caught 'em. 😄 As for the spaces between |
|
Haha that is just fine. I also wanted no spaces there but I could not configure it to remove spacing between anonymous functions and its brackets. :/ So I went with this style. Can you just take the patch for the first commit and close this? |
|
I think imma close this one because it no longer cleanly merges, and I tried to go manually address all the semi-colon issues - you cool with that? |
The first commit only adds semicolons and stuff.
In the second commit, I've run JS Beautifier (tabsize 2) over all the JS code. If you don't like its result (consistent use of spaces, mostly, after keywords), tell me, and I will produce a patch without it.
The annoying this of using 2 spaces instead of 4 spaces, is that Beautifier puts 1 tab (=2/4 spaces) in front of the require block elements. It lines up awesomely when using 4 spaces:
I do realize you might have your own config of a beautifier, or you TOTALLY hate this. Then I am sorry and I will remove it :P I just see this style a lot in Node.JS.