I like the idea of throwing this into a plugin. I think actually writing a
pake-task would be better, which is easily done as a plugin whereas a lime
test alone would require some meddling, I want something I can install and
type in a quick command (e.g. ./symfony how-is-my-code ;) )
-d
On 9/5/0
I would suggest that plugins are the best place for all additional
development of symfony. That way the core stays as lightweight as possible
and users can choose what elements suite their development practices. For
exmaple the control pannel is now a plugin and the audit could be part of
this.
I
Now when I think about it, should this be part of symfony itself? A
symfony tasks that will be easy to run as 'symfony codelint' or
something along those lines. Do people think this is important
especially for larger teams where you want to be sure standards are
being followed?
Kupo
Alexande
Jack,
I would be happy if you share that unit test code with us when you are
done or if you want some help, put it online and I will be also happy to
contribute.
Kupo
Jack Bates wrote:
> I'm working on an automated code audit, to check our code conforms to
> symfony's code standards. I'm curr
On 29 Aug 2007, at 20:29, Tristan Rivoallan wrote:
> On 8/29/07, Jack Bates <[EMAIL PROTECTED]> wrote:
>> I wonder if any code already exists for checking symfony's code
>> standards?
>
> pear's codesniffer can provide a very good basis for implementing
> this.
>
> http://pear.php.net/package/PH
hi,
On 8/29/07, Jack Bates <[EMAIL PROTECTED]> wrote:
> I wonder if any code already exists for checking symfony's code
> standards?
pear's codesniffer can provide a very good basis for implementing this.
http://pear.php.net/package/PHP_CodeSniffer
i guess it should not take too long to adapt
