Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.1.0

Bug #14251 --extensions option doesn't work
Submitted: 2008-06-27 14:36 UTC Modified: 2008-06-29 23:58 UTC
From: miau Assigned: squiz
Status: Closed Package: PHP_CodeSniffer (version 1.1.0RC2)
PHP Version: 5.2.5 OS:
Roadmaps: 1.1.0    
Subscription  


 [2008-06-27 14:36 UTC] miau (Koji Ando)
Description: ------------ Using --extensions option, no scripts are sniffed. Test script: --------------- >ls src foo.ctp foo.inc foo.php >phpcs --report=summary src PHP CODE SNIFFER REPORT SUMMARY -------------------------------------------------------------------------------- FILE ERRORS WARNINGS -------------------------------------------------------------------------------- D:\xampplite\php\src\foo.inc 5 0 D:\xampplite\php\src\foo.php 5 0 -------------------------------------------------------------------------------- A TOTAL OF 10 ERROR(S) AND 0 WARNING(S) WERE FOUND IN 2 FILE(S) -------------------------------------------------------------------------------- >phpcs --report=summary --extensions=inc,php,ctp src Expected result: ---------------- PHP CODE SNIFFER REPORT SUMMARY -------------------------------------------------------------------------------- FILE ERRORS WARNINGS -------------------------------------------------------------------------------- D:\xampplite\php\src\foo.inc 5 0 D:\xampplite\php\src\foo.php 5 0 D:\xampplite\php\src\foo.ctp 5 0 -------------------------------------------------------------------------------- A TOTAL OF 15 ERROR(S) AND 0 WARNING(S) WERE FOUND IN 3 FILE(S) -------------------------------------------------------------------------------- Actual result: -------------- (no output)

Comments

 [2008-06-29 23:58 UTC] squiz (Greg Sherwood)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.