Comments on DragonBe's PHP blog: Quality Assurance on PHP projects - PHP_CodeSniffe...

The blame report can also be done in Git (version ...

2011-08-06T18:31:28.083+02:00

The blame report can also be done in Git (version 1.3) and Hg (trunk) as long as you are within the checked out project.

Hi Michelangelo, Good thing to point out codesni...

2011-07-20T11:52:30.742+02:00

Hi Michelangelo,

Good thing to point out codesniffer. It's an easy to install/use tool.

Now lets all decide on one coding standard ;) I keep on having to switch different standards in different projects.

You don't have to keep specifying the standard...

2011-07-20T10:09:56.991+02:00

You don't have to keep specifying the standard to use on the command line - I guess you might be doing this here to iterate the point that there is more than one standard to choose from! Anyway, you can set a standard as the default one for PHPCS to check with:

sudo phpcs --config-set default_standard PEAR

There's a small gotcha here - you don't use an "=" sign when setting a value in your config.

For a simpler tool (less powerful but easy to conf...

2011-07-18T17:25:10.971+02:00

For a simpler tool (less powerful but easy to configure) you can also have a look at : http://code.google.com/p/phpcheckstyle/

I have enjoyed using the Drupal Standards with PHP...

2011-07-18T17:15:39.692+02:00

I have enjoyed using the Drupal Standards with PHPCS. They are well documented at http://drupal.org/coding-standard. In addition, there is a conversion script that can update code to resolve many common problems. It's been quite helpful with legacy code, and it runs fine as a standalone script. You can find it as coder_format.php in the drupal distribution.

In addition, PHPCS is a great tool to integrate with a Jenkins build system. I highly recommend looking at http://jenkins-php.org/ for information about integrating phpcs into a build system.

A quick note. On some Linux distributions, includi...

2011-07-18T11:45:23.691+02:00

A quick note. On some Linux distributions, including Fedora, php_codeSniffer can be installed using the distro tools:

su -c 'yum -y install php-pear-PHP-CodeSniffer'

And the run from the terminal:

phpcs --standard="foo" bar.php

For the lazy ones, with Zend Framework -Boilerplat...

2011-07-18T10:06:03.851+02:00

For the lazy ones, with Zend Framework -Boilerplate (https://github.com/michael-romer/zf-boilerplate) there is a tool available that builds you a full-featured virtual box for development including PHP_CodeSniffer. It has some other cool features in it as well so maybe this is of help to someone.

Michelangelo, Great post. I have been thinkering ...

2011-07-18T09:29:49.348+02:00

Michelangelo,

Great post. I have been thinkering with CodeSniffer lately and creating my own sniffs and standard. I'm planning to write a blog post about this soon. If anyone is interested in this sooner, ping me on irc (lineke) or twitter (@the_linie)

Nice, I would be interested if there was some good...

2011-07-18T06:51:11.587+02:00

Nice, I would be interested if there was some good tutorial on setting up small style changes.

I would not waste time to create entire new standard but maybe change the style little bit to match our preference :)

Would you recommend any good articles?

cheers

Art

I have been looking into setting this up at my wor...

2011-07-18T00:23:36.580+02:00

I have been looking into setting this up at my workplace - I got as far as starting to design my own standard, but I realized it's a lot of work to deviate and implement your own standard. It would be great if someone made a simple, configurable set of tests that are customizable in a similar way to NetBeans' code formatting (basically, a simple YAML file or something would suffice for my basic needs).

On the other hand, maybe this means PHPCS isn't the tool I am looking for, if all I want to do is analyze formatting. PHPCS can delve into much more advanced code analysis than the level I currently need.