FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=18125&edit=1

ID: 18125
Updated by: gsherwood@squiz.net
Reported By: cweiske at php dot net
Summary: Fatal error when excluded sniff does not exist
-Status: Assigned
+Status: Wont fix
Type: Feature/Change Request
Package: PHP_CodeSniffer
Package Version: 1.3.0RC1
PHP Version: Irrelevant
Assigned To: squiz
Roadmap Versions:
New Comment:

-Status: Assigned
+Status: Wont fix



Previous Comments:
------------------------------------------------------------------------

[2010-12-20 11:27:43] squiz

-Type: Bug
+Type: Feature/Change Request
-Assigned To:
+Assigned To: squiz
That's really a matter of opinion. If the standard is not valid, then I
don't think it should allow the standard to be used. While you may see
the warnings when running on the command line, others wont see them if
using IDE plugins or build systems. But they always see fatal errors.

------------------------------------------------------------------------

[2010-12-20 11:13:40] cweiske

Description:
------------
We have a custom coding standard that is based on the PEAR CS. In our
configuration file, we excluded some PEAR rules.

Now the new update (1.3.0RC1) removed a sniff that we excluded, and we
get a fatal error:
---
PHP Fatal error: Uncaught PHP_CodeSniffer_Exception: Referenced sniff
PEAR.Files.LineEndings does not exist in
/some/where/over/the/rainbow/PHP/CodeSniffer.php on line 638
---

Since it's an excluded sniff, phpcs should not crash but only show a
warning.

------------------------------------------------------------------------

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedJan 13, '11 at 12:03a
activeJan 13, '11 at 12:03a
posts1
users1
websitepear.php.net

1 user in discussion

Gsherwood: 1 post

People

Translate

site design / logo © 2022 Grokbase