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

Add 'dev:extension:fingerprint' #49

Open
peterjaap opened this issue Nov 18, 2016 · 1 comment
Open

Add 'dev:extension:fingerprint' #49

peterjaap opened this issue Nov 18, 2016 · 1 comment

Comments

@peterjaap
Copy link
Owner

I would like to have a command that fingerprints an extension. With that I mean a quick overview of functionality given by the extension and how it achieves that.

  • List of all files
  • Summary of;
  • Codepool, version (check against hypernode:modules:list-updates to see whether it is the latest version), package name, module name, depends
  • Block classes, model classes, helper classes, etc
  • Rewrites
  • The database schema changes it does
  • Layout updates (which handles does it touch, which static files are added, etc)
  • Routes
  • Event observers
  • ACL
  • Which config options does it set (config.xml default node)
  • Which config options are configurable (system.xml)
  • Old admin routing warning

Maybe we could test if the user running the command has Judge (or similar) installed. Or run the extension name through Triplecheck.io to check the quality of the extension.

@peterjaap
Copy link
Owner Author

Use case; when I need to install a new extension I quickly like to see what it does & touches. Automated rewrite conflicts check would be nice too.

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

No branches or pull requests

1 participant