Usually that's why it makes it easier to stock with a jshint file and a
specific coding style.

Here, we use the one that is provided with the push. And we stick with
Google styling guide so coders have a sense of reference.

The only other changes that I would like to make that have not been made
are with the if statements. They should all be closed, especially when
working with multiple developers. That is the easiest way to cause a
problem. Plus with the latest Javascript coming out, it will not only be
more object oriented but be more strict as well. So might as well start
getting used to the strict method now than later. ;)
On Apr 13, 2014 8:32 PM, "Giraldo Rosales" <nitrog7@gmail.com> wrote:

> I personally thought it was more of a standard more than a preference. Not
> sure where I've seen it not indented.
>
> If it really bothers you feel free to change it/overwrite it. I'll be sure
> not to clean up any other files. Makes it hard to contribute.
> On Apr 13, 2014 8:02 PM, "Charles Pick" <notifications@github.com> wrote:
>
>> In test/server/server-test.js:
>>
>> > @@ -1,101 +1,103 @@
>> > -var errors = LIB.errors;
>>
>> you reformatted the code to use indents when method chaining, I know this
>> is a preference, but I think this makes it very hard to follow when mixed
>> with e.g. if statements. Please could you undo it?
>>
>> —
>> Reply to this email directly or view it on GitHub<https://github.com/codemix/oriento/pull/24/files#r11568806>
>> .
>>
>