Exactly. So if you have preferences, make the changes after the merge. Most
editors will do this for you. Or have everyone run it through an auto
formatter. Or run a git hook to convert it on a pull. There are many ways
of achieving this without the use of a defined style.

Also by checking null/undefined without the use of "==" you can just do
if(!obj).


On Mon, Apr 14, 2014 at 10:42 AM, Charles Pick <notifications@github.com>wrote:

> In test/server/server-test.js:
>
> > @@ -1,101 +1,103 @@
> > -var errors = LIB.errors;
>
> The only places we use == over === are when we're doing a null/undefined
> check or we *want* type coercion - we're not using it by mistake, we're
> using it because it's the fastest way of doing what we want to do in V8. We
> do use camel case for everything apart from constants / global test helpers.
>
> You're right though, we're not strictly following a guide, and personally
> that does not bother me. I don't care about that. I care about a
> consistent, readable style and working code :)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/codemix/oriento/pull/24/files#r11587424>
> .
>