Re: phpcs throwing warnings on trivial things
| From: | till | Date: | Sat, 05 Apr 2008 11:35:45 +0000 |
| Subject: | Re: phpcs throwing warnings on trivial things | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-49629@lists.php.net to get a copy of this message | ||
On Sat, Apr 5, 2008 at 7:21 AM, Joe Stump <joe@joestump.net> wrote:
> (...)
> This phpcs stuff is 98% nonsense. I hope we're not actively keeping
> packages OUT of PEAR due to whether or not a package has 2 or 4 spaces after
> the @category tag. At least the package is documented. Bureaucracy gone wild
> if you ask me.
>
> If anyone needs me I'll be fixing 600+ trivial nonsensical "errors" in my
> code for Services_Facebook.
I agree that this is a pain in the buttocks to fix them. And I
wouldn't necessarily deny a package in PEAR just because of CS, but
where would you draw the line? Like, you are saying "2 or 4 spaces is
not a show-stopper", next person says, "but my method names are so
obvious, I don't need to document them" (just an example).
I totally feel you when you say it's non-sense because correcting them
is a lot of work and so on, but then again, a standard is a standard.
There is no 90% standard compliant, or 80%. There is just 100%.
If you want, I can help you fix the 600 over the weekend. :-)
Till