Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Package Characterizer #22

Open
josegonzalez opened this issue Jun 30, 2011 · 1 comment
Open

Better Package Characterizer #22

josegonzalez opened this issue Jun 30, 2011 · 1 comment

Comments

@josegonzalez
Copy link
Member

At the moment, the Package Characterization system uses token_get_all() to figure out what kind of code a particular project has. While nice, it does not detect whether a piece of code is following CakePHP standards, nor whether it is in a proper plugin/app format.

Ideally, we'd have a more robust package characterizer that would use ReflectionClass, but not bork on Fatal Errors from not being able to include files. The solution to this does not have to be in PHP.

@shama
Copy link
Contributor

shama commented Apr 5, 2012

I could write a simple script that evaluates a package structure / code use and rates it. We could also use CodeSniffer as well. It'll generate a lot of errors but we can play around with a good threshold number to factor in.

This seems related to #10 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants