You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: