CRM-20224 - Civi\ActionSchedule\Events - Rename internal events (`actionSchedule...
authorTim Otten <totten@civicrm.org>
Tue, 7 Mar 2017 08:17:32 +0000 (00:17 -0800)
committerTim Otten <totten@civicrm.org>
Tue, 7 Mar 2017 08:47:52 +0000 (00:47 -0800)
commitfa6fce2f06fba0d4a7c5454e34c0184589f8be05
tree8748b8c8fe5640024b75027f924155efe919b3c0
parentf247addc55ecf9e35dbd1afd8c8da044bef7a3c3
CRM-20224 - Civi\ActionSchedule\Events - Rename internal events (`actionSchedule.fooBar` vs `civi.actionSchedule.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 `actionSchedule.fooBar` convention.  Based on
grepping universe, I don't believe any extensions rely on the `DAO::*`
events.
Civi/ActionSchedule/Events.php