CRM-20224 - CRM_Core_DAO - Rename internal events (`DAO::foo-bar` vs `civi.dao.fooBar`)
authorTim Otten <totten@civicrm.org>
Fri, 3 Mar 2017 22:43:27 +0000 (14:43 -0800)
committerTim Otten <totten@civicrm.org>
Tue, 7 Mar 2017 08:47:42 +0000 (00:47 -0800)
commit9407546428fd44e96a457c67fe81b568e724911b
tree8d1a468457100b641b7da4681a2a8d3013013a12
parent6b15c957f401213017ed76c24b8de34376ddbda8
CRM-20224 - CRM_Core_DAO - Rename internal events (`DAO::foo-bar` vs `civi.dao.fooBar`)

If you look at the list of events emitted through the EventDispatcher, you'll
find several different formats for the names:

```
   actionSchedule.getMappings
   actionSchedule.prepareMailingQuery
   api.authorize
   api.exception
   api.prepare
   api.resolve
   api.respond
   civi.core.install
   civi.token.eval
   civi.token.list
   civi.token.render
   DAO::post-delete
   DAO::post-insert
   DAO::post-update
   hook_civicrm_caseChange
   hook_civicrm_post::Activity
   hook_civicrm_post::Case
   hook_civicrm_unhandled_exception
```

This patch renames events using the `DAO::foo-bar` convention.  Based on
grepping universe, I don't believe any extensions rely on the `DAO::*`
events.
CRM/Core/DAO.php
Civi/Core/Container.php