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

Bug #12645 error message is wrong.
Submitted: 2007-12-09 15:01 UTC
From: renoiv Assigned: squiz
Status: Closed Package: PHP_CodeSniffer (version 1.0.0RC3)
PHP Version: 5.2.5 OS:
Roadmaps: 1.0.0    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 13 + 12 = ?

 
 [2007-12-09 15:01 UTC] renoiv (renoiv)
Description: ------------ The error message of Squiz_Sniffs_Arrays_ArrayDeclarationSniff is wrong. I am not good at English. If a sentence of this bug is a unclear meaning, I am sorry. Test script: --------------- <?php $value = in_array('1', array('1' , '2')); ?> Expected result: ---------------- [test@]$ phpcs --standard=Squiz ArrayDeclarationTest.php FILE: ArrayDeclarationTest.php -------------------------------------------------------------------------------- FOUND 2 ERROR(S) AND 0 WARNING(S) AFFECTING 1 LINE(S) -------------------------------------------------------------------------------- 2 | ERROR | Missing file doc comment 2 | ERROR | Expected 0 space between "'1'" and comma; 2 found -------------------------------------------------------------------------------- Actual result: -------------- [test@]$ phpcs --standard=Squiz ArrayDeclarationTest.php FILE: ArrayDeclarationTest.php -------------------------------------------------------------------------------- FOUND 2 ERROR(S) AND 0 WARNING(S) AFFECTING 1 LINE(S) -------------------------------------------------------------------------------- 2 | ERROR | Missing file doc comment 2 | ERROR | Expected 1 space between "'1'" and comma; 2 found --------------------------------------------------------------------------------

Comments

 [2007-12-10 04:01 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.