http://pear.php.net/bugs/search.php?cmd=display&package_name%5B0%5D=PHP_CodeSniffer Search Results en-us pear-webmaster@lists.php.net pear-webmaster@lists.php.net hourly 1 2000-01-01T12:00+00:00 http://pear.php.net/gifs/pearsmall.gif http://pear.php.net/bugs http://pear.php.net/bugs/16836 PHP_CodeSniffer Bug Reported by marynicolehicks 2009-11-26T05:11:10+00:00 PHP: 5.2.5 OS: Windows Vista 32 Package Version: 1.2.1 Description: ------------ NOTICE: Undefined index: scope_closer in D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php on line 459 Test script: --------------- Should be easy to spot in the code. Expected result: ---------------- Expect no notices in logs. Actual result: -------------- 2009-11-26T16:54:15+13:00 ERR (3): NOTICE: Undefined index: scope_closer in D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php on line 459 #0 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php(459): My_Log->LogErrorHandler(8, 'Undefined index...', 'D:\My Documents...', 459, Array) #1 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(772): PHP_CodeSniffer_Tokenizers_PHP->processAdditional(Array, '??') #2 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(512): PHP_CodeSniffer_File::tokenizeString('<?php????/**?? ...', Object(PHP_CodeSniffer_Tokenizers_PHP), '??') #3 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(362): PHP_CodeSniffer_File->_parse(NULL) #4 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(784): PHP_CodeSniffer_File->start(NULL) #5 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(690): PHP_CodeSniffer->processFile('D:\My Documents...') #6 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(341): PHP_CodeSniffer->processFiles('D:\My Documents...', false) #7 D:\My Documents\My Websites\DreamHost\fms\test\CodeSniffer\RunCodeSniffer.php(20): PHP_CodeSniffer->process(Array, 'D:\My Documents...') #8 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(173): include('D:\My Documents...') #9 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(108): UnitTests->runCodeSniffer() #10 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(78): UnitTests->__construct(Object(Zend_Console_Getopt)) #11 {main}]]> PHP_CodeSniffer Bug Reported by marynicolehicks 2009-11-26T05:11:10+00:00 PHP: 5.2.5 OS: Windows Vista 32 Package Version: 1.2.1 Description: ------------ NOTICE: Undefined index: scope_closer in D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php on line 459 Test script: --------------- Should be easy to spot in the code. Expected result: ---------------- Expect no notices in logs. Actual result: -------------- 2009-11-26T16:54:15+13:00 ERR (3): NOTICE: Undefined index: scope_closer in D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php on line 459 #0 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\Tokenizers\PHP.php(459): My_Log->LogErrorHandler(8, 'Undefined index...', 'D:\My Documents...', 459, Array) #1 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(772): PHP_CodeSniffer_Tokenizers_PHP->processAdditional(Array, '??') #2 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(512): PHP_CodeSniffer_File::tokenizeString('<?php????/**?? ...', Object(PHP_CodeSniffer_Tokenizers_PHP), '??') #3 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer\File.php(362): PHP_CodeSniffer_File->_parse(NULL) #4 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(784): PHP_CodeSniffer_File->start(NULL) #5 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(690): PHP_CodeSniffer->processFile('D:\My Documents...') #6 D:\My Documents\My Websites\DreamHost\fms\library\Pear\pear\PHP\CodeSniffer.php(341): PHP_CodeSniffer->processFiles('D:\My Documents...', false) #7 D:\My Documents\My Websites\DreamHost\fms\test\CodeSniffer\RunCodeSniffer.php(20): PHP_CodeSniffer->process(Array, 'D:\My Documents...') #8 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(173): include('D:\My Documents...') #9 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(108): UnitTests->runCodeSniffer() #10 D:\My Documents\My Websites\DreamHost\fms\test\UnitTests.php(78): UnitTests->__construct(Object(Zend_Console_Getopt)) #11 {main}]]> 2009-11-26T10:22:46+00:00 xxx &#x61;&#116; marynicolehicks &#x64;&#111;&#x74; com PHP_CodeSniffer Bug http://pear.php.net/bugs/16740 PHP_CodeSniffer Bug Reported by sebastian 2009-10-25T18:32:36+00:00 PHP: 5.3.0 OS: Irrelevant Package Version: 1.2.0 Description: ------------ A function or method parameter that is only used in an heredoc string is reported as not being used. Test script: --------------- <?php function foo($bar) { print <<<BAZ ... $bar ... BAZ } Expected result: ---------------- No violation. Actual result: -------------- FILE: /home/sb/test.php -------------------------------------------------------------------------------- FOUND 0 ERROR(S) AND 1 WARNING(S) AFFECTING 1 LINE(S) -------------------------------------------------------------------------------- 2 | WARNING | The method parameter $bar is never used --------------------------------------------------------------------------------]]> PHP_CodeSniffer Bug Reported by sebastian 2009-10-25T18:32:36+00:00 PHP: 5.3.0 OS: Irrelevant Package Version: 1.2.0 Description: ------------ A function or method parameter that is only used in an heredoc string is reported as not being used. Test script: --------------- <?php function foo($bar) { print <<<BAZ ... $bar ... BAZ } Expected result: ---------------- No violation. Actual result: -------------- FILE: /home/sb/test.php -------------------------------------------------------------------------------- FOUND 0 ERROR(S) AND 1 WARNING(S) AFFECTING 1 LINE(S) -------------------------------------------------------------------------------- 2 | WARNING | The method parameter $bar is never used --------------------------------------------------------------------------------]]> 2009-10-25T18:32:36+00:00 sb &#x61;&#116; sebastian-bergmann &#x64;&#111;&#x74; de PHP_CodeSniffer Bug http://pear.php.net/bugs/16694 PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-10-12T13:49:24+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ A specialization of Generic_Sniffs_PHP_ForbiddenFunctionsSniff would be nice that scans for deprecated functions in PHP. Please find a proof-of-concept implementation attached.]]> PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-10-12T13:49:24+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ A specialization of Generic_Sniffs_PHP_ForbiddenFunctionsSniff would be nice that scans for deprecated functions in PHP. Please find a proof-of-concept implementation attached.]]> 2009-10-12T13:49:24+00:00 sb &#x61;&#116; sebastian-bergmann &#x64;&#111;&#x74; de PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/16693 PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-10-12T13:13:33+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ Running phpcs on a large code base in the context of continuous integration can be very time consuming. Just because a couple of files have changed (for which phpcs would run for a couple of seconds or minutes) should not mean that phpcs needs to be run for all files again (which can take an hour). It would be beneficial if phpcs could be pointed to a previously generated Checkstyle XML logfile and be given a list of changed files. It would then scan the changed files and update the relevant sections of the Checkstyle XML logfile. I am not entirely sure whether this functionality belongs into phpcs itself or if it should be implemented in phpUnderControl, for instance.]]> PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-10-12T13:13:33+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ Running phpcs on a large code base in the context of continuous integration can be very time consuming. Just because a couple of files have changed (for which phpcs would run for a couple of seconds or minutes) should not mean that phpcs needs to be run for all files again (which can take an hour). It would be beneficial if phpcs could be pointed to a previously generated Checkstyle XML logfile and be given a list of changed files. It would then scan the changed files and update the relevant sections of the Checkstyle XML logfile. I am not entirely sure whether this functionality belongs into phpcs itself or if it should be implemented in phpUnderControl, for instance.]]> 2009-10-12T13:13:33+00:00 sb &#x61;&#116; sebastian-bergmann &#x64;&#111;&#x74; de PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/16209 PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-05-09T10:12:30+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ A case of "useless tests" that I see from time to time is that developers write tests that execution SUT code without asserting -- thus not actually testing -- anything. The sniff should raise a warning when the following conditions are met: - Class has PHPUnit_Framework_TestCase as an ancestor - Method is public and has name test*() or the @test annotation - The method itself (and other methods called from it) does not call $this->assert*(), self::assert*(), or PHPUnit_Framework_Assert::assert*() and does not set up a mock object with expectations. Test script: --------------- . Expected result: ---------------- . Actual result: -------------- .]]> PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-05-09T10:12:30+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ A case of "useless tests" that I see from time to time is that developers write tests that execution SUT code without asserting -- thus not actually testing -- anything. The sniff should raise a warning when the following conditions are met: - Class has PHPUnit_Framework_TestCase as an ancestor - Method is public and has name test*() or the @test annotation - The method itself (and other methods called from it) does not call $this->assert*(), self::assert*(), or PHPUnit_Framework_Assert::assert*() and does not set up a mock object with expectations. Test script: --------------- . Expected result: ---------------- . Actual result: -------------- .]]> 2009-07-02T07:41:32+00:00 sb &#x61;&#116; sebastian-bergmann &#x64;&#111;&#x74; de PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/16163 PHP_CodeSniffer Feature/Change Request Reported by gimler 2009-04-30T09:28:04+00:00 PHP: 5.2.9 OS: Package Version: 1.2.0RC1 Description: ------------ please move the hardcoded value in file PEAR/Sniffs/Commenting/FileCommentSniff.php at line 287+578 to a property to easy override when i extends this class in my own standard. tanks]]> PHP_CodeSniffer Feature/Change Request Reported by gimler 2009-04-30T09:28:04+00:00 PHP: 5.2.9 OS: Package Version: 1.2.0RC1 Description: ------------ please move the hardcoded value in file PEAR/Sniffs/Commenting/FileCommentSniff.php at line 287+578 to a property to easy override when i extends this class in my own standard. tanks]]> 2009-07-02T07:38:25+00:00 gfranke &#x61;&#116; savedcite &#x64;&#111;&#x74; com PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/16114 PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-04-17T10:54:15+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ Multi-File/Multi-Pass sniff that first collects a list of all declared functions and methods and then checks whether each is called at least once. A function/method that is not called should then be reported as an error.]]> PHP_CodeSniffer Feature/Change Request Reported by sebastian 2009-04-17T10:54:15+00:00 PHP: Irrelevant OS: Irrelevant Package Version: CVS Description: ------------ Multi-File/Multi-Pass sniff that first collects a list of all declared functions and methods and then checks whether each is called at least once. A function/method that is not called should then be reported as an error.]]> 2009-07-02T07:31:10+00:00 sb &#x61;&#116; sebastian-bergmann &#x64;&#111;&#x74; de PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/15865 PHP_CodeSniffer Feature/Change Request Reported by dfgsdfgsdfgdff 2009-02-02T15:08:59+00:00 PHP: 5.2.4 OS: Package Version: 1.2.0a1 Description: ------------ It would be great if codesniffer could help ensure code is multibyte. This would mean adding a sniff that does not allow the use of strlen (should use mb_strlen) etc.]]> PHP_CodeSniffer Feature/Change Request Reported by dfgsdfgsdfgdff 2009-02-02T15:08:59+00:00 PHP: 5.2.4 OS: Package Version: 1.2.0a1 Description: ------------ It would be great if codesniffer could help ensure code is multibyte. This would mean adding a sniff that does not allow the use of strlen (should use mb_strlen) etc.]]> 2009-07-02T07:24:42+00:00 pear &#x61;&#116; infoweb &#x64;&#111;&#x74; co &#x64;&#111;&#x74; nz PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/15338 PHP_CodeSniffer Feature/Change Request Reported by squiz 2008-12-17T18:09:36+00:00 PHP: Irrelevant OS: Any Package Version: CVS Description: ------------ A new INFO message level, hidden by default, would allow standards to include additional checks that users could turn on to try and meet a higher level of standard. Examples of standards that may benefit are Line Length and Cyclomatic Complexity, which are useful but not always integrated into a standard offically.]]> PHP_CodeSniffer Feature/Change Request Reported by squiz 2008-12-17T18:09:36+00:00 PHP: Irrelevant OS: Any Package Version: CVS Description: ------------ A new INFO message level, hidden by default, would allow standards to include additional checks that users could turn on to try and meet a higher level of standard. Examples of standards that may benefit are Line Length and Cyclomatic Complexity, which are useful but not always integrated into a standard offically.]]> 2008-12-18T18:58:40+00:00 gsherwood &#x61;&#116; squiz &#x64;&#111;&#x74; net PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/14699 PHP_CodeSniffer Feature/Change Request Reported by beyer 2008-09-24T05:59:13+00:00 PHP: 5.2.1 OS: Linux Package Version: 1.1.0 Description: ------------ The PEAR FileCommentSniff is quite unextendable due to the weak docblock choice. File Comments are falsely returned as wrong class comments.]]> PHP_CodeSniffer Feature/Change Request Reported by beyer 2008-09-24T05:59:13+00:00 PHP: 5.2.1 OS: Linux Package Version: 1.1.0 Description: ------------ The PEAR FileCommentSniff is quite unextendable due to the weak docblock choice. File Comments are falsely returned as wrong class comments.]]> 2008-11-13T17:59:04+00:00 m &#x64;&#111;&#x74; beyer5 &#x61;&#116; gmx &#x64;&#111;&#x74; de PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/14237 PHP_CodeSniffer Feature/Change Request Reported by miau 2008-06-25T11:18:53+00:00 PHP: 5.2.5 OS: Package Version: 1.1.0RC2 Description: ------------ While most multi-byte characters are reprenseted by 3 octet in UTF-8, they take up 2 character widths. Test script: --------------- >cat php.ini | grep mbstring.internal_encoding mbstring.internal_encoding = UTF-8 ; mbstring.internal_encoding setting. Input chars are ; given by corresponding encode setting. When empty mbstring.internal_encoding >php -i | grep mbstring.internal_encoding mbstring.internal_encoding => UTF-8 => UTF-8 >phpcs --standard=Zend multi_byte_sample.php Expected result: ---------------- 2 | WARNING | Line exceeds 80 characters; contains 81 characters Actual result: -------------- 2 | WARNING | Line exceeds 80 characters; contains 86 characters]]> PHP_CodeSniffer Feature/Change Request Reported by miau 2008-06-25T11:18:53+00:00 PHP: 5.2.5 OS: Package Version: 1.1.0RC2 Description: ------------ While most multi-byte characters are reprenseted by 3 octet in UTF-8, they take up 2 character widths. Test script: --------------- >cat php.ini | grep mbstring.internal_encoding mbstring.internal_encoding = UTF-8 ; mbstring.internal_encoding setting. Input chars are ; given by corresponding encode setting. When empty mbstring.internal_encoding >php -i | grep mbstring.internal_encoding mbstring.internal_encoding => UTF-8 => UTF-8 >phpcs --standard=Zend multi_byte_sample.php Expected result: ---------------- 2 | WARNING | Line exceeds 80 characters; contains 81 characters Actual result: -------------- 2 | WARNING | Line exceeds 80 characters; contains 86 characters]]> 2008-06-30T00:00:39+00:00 miau &#x64;&#111;&#x74; jp &#x61;&#116; gmail &#x64;&#111;&#x74; com PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/14074 PHP_CodeSniffer Feature/Change Request Reported by doconnor 2008-06-04T22:14:57+00:00 PHP: 5.2.6 OS: Package Version: 1.0.1 Description: ------------ One of the things which is really neat in PHPUnit is the ability to log a run into a database. Scenario: An organization runs unit tests, documentation, etc nightly. They wish to provide an easily queried set of data about coding style / standards - this enables them to examine it in the same tool as other logged data. The codebase is significant, and makes the use of XML hard to scale (performance).]]> PHP_CodeSniffer Feature/Change Request Reported by doconnor 2008-06-04T22:14:57+00:00 PHP: 5.2.6 OS: Package Version: 1.0.1 Description: ------------ One of the things which is really neat in PHPUnit is the ability to log a run into a database. Scenario: An organization runs unit tests, documentation, etc nightly. They wish to provide an easily queried set of data about coding style / standards - this enables them to examine it in the same tool as other logged data. The codebase is significant, and makes the use of XML hard to scale (performance).]]> 2009-05-04T14:31:26+00:00 daniel &#x64;&#111;&#x74; oconnor &#x61;&#116; gmail &#x64;&#111;&#x74; com PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/13813 PHP_CodeSniffer Feature/Change Request Reported by blacksheepkhan 2008-04-30T15:50:03+00:00 PHP: Irrelevant OS: Irrelevant Package Version: 1.1.0a1 Description: ------------ When the new ScopeIndentSniff is being extended to switch the "exact" boolean parameter on then it does not take in account doc indents. Reason: We want to have all indents fixed to 4 spaces, not more. But documentation (inline) lines should be ignored because they are checked elsewhere. Test script: --------------- class anything { /** * test */ public function xxxx Expected result: ---------------- No report expected because doc starts with 4 spaces and public also... The 1 space difference from within the doc (line * test and */) should be ignored. Actual result: -------------- Switching "exact" on throws error on "* test" and "*/" being 5 chars indent. Switching "exact" would not throw an error when indention is more than 4 for public or other lines.]]> PHP_CodeSniffer Feature/Change Request Reported by blacksheepkhan 2008-04-30T15:50:03+00:00 PHP: Irrelevant OS: Irrelevant Package Version: 1.1.0a1 Description: ------------ When the new ScopeIndentSniff is being extended to switch the "exact" boolean parameter on then it does not take in account doc indents. Reason: We want to have all indents fixed to 4 spaces, not more. But documentation (inline) lines should be ignored because they are checked elsewhere. Test script: --------------- class anything { /** * test */ public function xxxx Expected result: ---------------- No report expected because doc starts with 4 spaces and public also... The 1 space difference from within the doc (line * test and */) should be ignored. Actual result: -------------- Switching "exact" on throws error on "* test" and "*/" being 5 chars indent. Switching "exact" would not throw an error when indention is more than 4 for public or other lines.]]> 2008-05-04T17:48:49+00:00 thomas &#x64;&#111;&#x74; weidner &#x61;&#116; gmx &#x64;&#111;&#x74; at PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/13774 PHP_CodeSniffer Feature/Change Request Reported by toxygene 2008-04-25T09:47:49+00:00 PHP: Irrelevant OS: Package Version: 1.0.1 Description: ------------ The Zend Framework is developing it's own PHPCS standard files (http://framework.zend.com/svn/framework/trunk/incubator/tools/codingstandard/), but the name conflicts with the existing Zend standard in PHPCS. I think it would make sense to remove the current Zend standard, or make it into a separate package (or make all the standards into separate packages).]]> PHP_CodeSniffer Feature/Change Request Reported by toxygene 2008-04-25T09:47:49+00:00 PHP: Irrelevant OS: Package Version: 1.0.1 Description: ------------ The Zend Framework is developing it's own PHPCS standard files (http://framework.zend.com/svn/framework/trunk/incubator/tools/codingstandard/), but the name conflicts with the existing Zend standard in PHPCS. I think it would make sense to remove the current Zend standard, or make it into a separate package (or make all the standards into separate packages).]]> 2008-06-29T05:47:38+00:00 justin &#x64;&#111;&#x74; hendrickson &#x61;&#116; gmail &#x64;&#111;&#x74; com PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/12544 PHP_CodeSniffer Feature/Change Request Reported by farell 2007-11-28T17:07:36+00:00 PHP: 5.2.4 OS: Windows XP Package Version: 1.0.0RC2 Description: ------------ phpcs CLI has already an option to ignore file(s) and directory(ies) from parsing. phpcs [--ignore=<pattern>] <file> Is it possible to change/upgrade its behavior and allow to : READ a .cvsignore file contents to ignore all files/dir identified inside. PEAR_PackageFileManager has something equivalent : @see [1] lines 106+ 109 (for merging options) Why I ask this ? Because I think it could be usefull when a batch script run a large analysis of many files/packages (as Christian Weiske did [2]) and we don't know (for each package) what are the files to exclude. Also, consider that command line as a limit, and we can expect to have a command like : phpcs --ignore=blah,blah,blah,blah,blah,blah,blah,blah,blah .... blah,blah,blah, ... very long list ...,blah,blah <file> Example : Yesterday I've commit some CS fixes on HTML_CSS, and I don't touched to CSS\Advanced.php because it's an old file written by Klaus Guenther. And this file was never be included in any public PEAR release of package HTML_CSS. Report of Christian [2] is in this way a bit bogus, because CSS\Advanced.php is included and gave me again 42 errors and 12 warnings, while I just hope to have 12 errors and 0 warnings with phpcs 1.0.0RC2, and 0 error, 0 warning when 1.0.0RC3 will be released (fixing @throws tag must contain a comment) Thanks Greg ! [1] http://cvs.php.net/viewvc.cgi/pear/PEAR_PackageFileManager/PackageFileManager/Cvs.php?annotate=1.15 [2] http://pear.cweiske.de/overview.htm]]> PHP_CodeSniffer Feature/Change Request Reported by farell 2007-11-28T17:07:36+00:00 PHP: 5.2.4 OS: Windows XP Package Version: 1.0.0RC2 Description: ------------ phpcs CLI has already an option to ignore file(s) and directory(ies) from parsing. phpcs [--ignore=<pattern>] <file> Is it possible to change/upgrade its behavior and allow to : READ a .cvsignore file contents to ignore all files/dir identified inside. PEAR_PackageFileManager has something equivalent : @see [1] lines 106+ 109 (for merging options) Why I ask this ? Because I think it could be usefull when a batch script run a large analysis of many files/packages (as Christian Weiske did [2]) and we don't know (for each package) what are the files to exclude. Also, consider that command line as a limit, and we can expect to have a command like : phpcs --ignore=blah,blah,blah,blah,blah,blah,blah,blah,blah .... blah,blah,blah, ... very long list ...,blah,blah <file> Example : Yesterday I've commit some CS fixes on HTML_CSS, and I don't touched to CSS\Advanced.php because it's an old file written by Klaus Guenther. And this file was never be included in any public PEAR release of package HTML_CSS. Report of Christian [2] is in this way a bit bogus, because CSS\Advanced.php is included and gave me again 42 errors and 12 warnings, while I just hope to have 12 errors and 0 warnings with phpcs 1.0.0RC2, and 0 error, 0 warning when 1.0.0RC3 will be released (fixing @throws tag must contain a comment) Thanks Greg ! [1] http://cvs.php.net/viewvc.cgi/pear/PEAR_PackageFileManager/PackageFileManager/Cvs.php?annotate=1.15 [2] http://pear.cweiske.de/overview.htm]]> 2008-02-20T17:37:21+00:00 pear &#x61;&#116; laurent-laville &#x64;&#111;&#x74; org PHP_CodeSniffer Feature/Change Request http://pear.php.net/bugs/12434 PHP_CodeSniffer Feature/Change Request Reported by cweiske 2007-11-13T06:32:37+00:00 PHP: Irrelevant OS: Package Version: 1.0.0RC1 Description: ------------ It would be cool if one could use several output renderers at once. This would require that an output file could be specified at command line. The feature is neccessary when you e.g. want to generate a complete overview about all files for developers, but only a short summary for status emails. One solution would be to export to xml, and render the xml yourself - but phpcs already has the ability to render txt files, so I don't see why I should reinvent that. I don't know how you implemented rendering, but IMO it'd be good if there'd be a "root renderer" that is used by phpcs internally. this renderer dispatches the logs to all registered renderer objects. That would allow using unlimited renderers for a phpcs sniff call. See http://pear.php.net/package/Event_Dispatcher which does it similar.]]> PHP_CodeSniffer Feature/Change Request Reported by cweiske 2007-11-13T06:32:37+00:00 PHP: Irrelevant OS: Package Version: 1.0.0RC1 Description: ------------ It would be cool if one could use several output renderers at once. This would require that an output file could be specified at command line. The feature is neccessary when you e.g. want to generate a complete overview about all files for developers, but only a short summary for status emails. One solution would be to export to xml, and render the xml yourself - but phpcs already has the ability to render txt files, so I don't see why I should reinvent that. I don't know how you implemented rendering, but IMO it'd be good if there'd be a "root renderer" that is used by phpcs internally. this renderer dispatches the logs to all registered renderer objects. That would allow using unlimited renderers for a phpcs sniff call. See http://pear.php.net/package/Event_Dispatcher which does it similar.]]> 2008-02-20T17:37:09+00:00 cweiske &#x61;&#116; php &#x64;&#111;&#x74; net PHP_CodeSniffer Feature/Change Request