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.

Sign up for GitHub

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

Jump to bottom

Show extension hooks #6

Open
xurizaemon opened this issue Mar 26, 2017 · 0 comments
Open

Show extension hooks #6

xurizaemon opened this issue Mar 26, 2017 · 0 comments

Comments

@xurizaemon
Copy link

Currently we just use Reflection to inspect the core CRM_Utils_Hook, where all hooks live in CiviCRM. A good addition would be to expose extension hooks as well.

We may need to denote the two differently, eg civicrm.hook_civicrm_config versus example.hook_civicrm_example?
@xurizaemon xurizaemon mentioned this issue Mar 31, 2017
Closed
xurizaemon added a commit that referenced this issue Apr 14, 2017
@xurizaemon
Use Civi Event Inspector to detect hooks. Refs #6, #8.
704735d 
Use \Civi\Core\CiviEventInspector() to identify events, hooks.

This is based on civicrm/civicrm-core#10161 which is WIP currently.

Refs #6, #8.
Refs civicrm/civicrm-core#10161.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xurizaemon