Feature: maintain coding style using PHP Code Sniffer

[koenpunt]

Added PHP Code Sniffer as composer dependency and to Travis config.

This is probably the time to switch to more sensible defaults:
tabs or spaces
OpeningFunctionBraceBsdAllman or OpeningFunctionBraceKernighanRitchie

[Rican7]

It would be ideal to conform to PSR-2... but that would be a huge BC break, since it would require changing the name of every single method. Lol.

In the meantime, its still better to ensure that we maintain the somewhat strange style of this project than have mixed YOLO styles. :P

[Rican7]

Here's a convenient review link to review the changes while ignoring whitespace:
https://github.com/jpfuentes2/php-activerecord/pull/469/files?w=1

[Rican7]

This looks good to me 👍

[koenpunt]

Does PSR requires a coding style for method names? I'd though it was only for project/class structures. But I did not read into it at all, so don't know..

[Rican7]

Yea. PSR-2 is an extension of PSR-1, which requires method names to be camel-cased:

https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md#43-methods

[cvanschalkwijk]

PSR-2 will need to wait until a major point release where BC will not be an issue. As for tabs and spaces, let's go with 4 spaces. I believe @jpfuentes2 is on board with that as well.