| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 3.7.2 |
| Request #16163 | Allow error messges to be overridden when extended sniffs | ||
|---|---|---|---|
| Submitted: | 2009-04-30 14:28 UTC | ||
| From: | gimler | Assigned: | squiz |
| Status: | Closed | Package: | PHP_CodeSniffer (version 1.2.0RC1) |
| PHP Version: | 5.2.9 | OS: | |
| Roadmaps: | (Not assigned) | ||
[2009-04-30 14:28 UTC] gimler
(Gordon Franke)
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
Comments
[2009-04-30 19:44 UTC] gimler
(Gordon Franke)
-Package Version: 1.1.0
+Package Version: 1.2.0RC1
in the version 1.2.0RC1 the hardcoded values are in line 356+660
in line 193 is another hardcoded value in the error message
$error = 'You must use "/**" style comments for a file comment'; [2009-07-02 12:38 UTC] squiz
(Greg Sherwood)
-Summary: move hardcoded class name to property
+Summary: Allow error messges to be overridden when
extended sniffs
-Status: Open
+Status: Assigned
-Assigned To:
+Assigned To: squiz
I wont be making this change, but I'll leave the report open and rename it.
What this really needs is the ability for all messages to be overwritten. There is no point doing it for a single sniff. [2010-02-18 05:33 UTC] squiz
(Greg Sherwood)
-Status: Assigned
+Status: Closed
You can now override message using a rulset.xml file in the SVN version:
http://www.squizlabs.com/php-codesniffer/php_codesniffer-ruleset.xml-support-in-svn