gsherwood

{
  "Arrays":{
    "Array keyword case":{
      "sniffs":{
        "0":"Squiz.Arrays.ArrayDeclaration"
      },
      "total":94079,
      "values":{
        "lower":94077,
        "upper":2

gsherwood

Running with a single standard will allow sniffs in that standard to add metrics about the source code.
This is a good way to get a feel for how a code base is deviating from a standard and ways you can
tweak the standard to more closely match what the majority of developers are doing.

The report output is still very rough, so read output like this:
    Function openning brace placement: new line [10431/10598, 98.42%]
        same line => 167 (1.58%)

as this:
    The majority of function openning braces are placed on a new line (98.42%).

gsherwood

$ git diff
diff --git a/CodeSniffer/File.php b/CodeSniffer/File.php
index f45e307..e629fed 100644
--- a/CodeSniffer/File.php
+++ b/CodeSniffer/File.php
@@ -1446,7 +1446,7 @@ class PHP_CodeSniffer_File
                 if (PHP_CODESNIFFER_VERBOSITY > 1) {
                     $type    = $tokens[$i]['type'];
                     $content = str_replace($eolChar, '\n', $tokens[$i]['content']);
-                    echo "\tStart scope map at $i: $type => $content".PHP_EOL;

gsherwood

$ php scripts/phpcs ../zf2/library/Zend/ --standard=PSR2 -p --report=source -ns

PHP CODE SNIFFER VIOLATION SOURCE SUMMARY
--------------------------------------------------------------------------------
    SOURCE                                                                 COUNT
--------------------------------------------------------------------------------
[x] PSR2.Methods.FunctionCallSignature.Indent                              328
[ ] PSR2.Methods.FunctionCallSignature.MultipleArguments                   276
[x] PSR2.Methods.FunctionCallSignature.CloseBracketLine                    248
[x] Squiz.WhiteSpace.ScopeClosingBrace.ContentBefore                       230