Re: PHP_CodeSniffer as part of the pepr proposal process

Greg Sherwood wrote: > Daniel O'Connor wrote: >> How difficult would it be to provide: >> >> 1. really clear directions on installing and running PHP_CodeSniffer >> over your proprosal >> 2. (and most desirable) the ability for a proposal (phps; or archive) >> to be evaluated automatically with PHP_CodeSniffer against PEAR >> standards >> before allowing a package to go from proposed to call for votes (or >> whatever >> stage you want to put it at)? > I'll let someone who knows PEPr comment on how easy this would be, but I > thought I'd show the output of PHP_CodeSniffer on PHP_Callback so people > can see some sample output. All the errors relate to commenting in this > case and so are fairly picky. > > Greg Hi Greg, I would be interested in investigating setting up codesniffer as a cron job for checking PEPr proposals. I'm assuming it would time out if used to check a large proposal. Have you tried it on something vast like phpDocumentor? Thanks, Greg