Task #38526
Format source code to PEAR standard
| Status: | Closed | Start date: | 2012-07-01 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Andy Grunwald | % Done: | 0% |
|
| Category: | Stuff | Spent time: | - | |
| Target version: | 0.0.4 | |||
| Branch: | Tags: | |||
| Votes: | 0 |
Description
PHP_CodeSniffer is source code which underlies the PEAR CodingGuidelines.
As we develop sniffs for the CodeSniffer, we take the decision to develpot our source code under the PEAR CGL as well.
So, one task is to format our source that this will match the CGL of PEAR.
Greg Sherwood wrote: Yes, the PHP_CodeSniffer deliviers a standard which is named "PHPCS". This is not the standard FOR the PHP_CodeSniffer. I`ve written a mail to Greg about this question and the answered, that the PHPCS standard that comes with PHPCS is basically just the PEAR standard and most of the Squiz standard. This is more strict and conforms more to what standard he use at work. <pre>
Related issues
| duplicates PHP_CodeSniffer - Bug #41164: Make Travis-CI-Build green! | Closed | 2012-09-21 |
History
Updated by Stefano Kowalke 8 months ago
- Status changed from New to Accepted
- Target version set to 0.0.4
Updated by Andy Grunwald 8 months ago
- Status changed from Accepted to Resolved
- Assignee set to Andy Grunwald
This task was solved by #41164
Updated by Andy Grunwald 8 months ago
- Status changed from Resolved to Closed