CRM-20224 - Civi\API\Events - Rename internal events (`api.foo` vs `civi.api.foo`)
authorTim Otten <totten@civicrm.org>
Tue, 7 Mar 2017 08:14:55 +0000 (00:14 -0800)
committerTim Otten <totten@civicrm.org>
Tue, 7 Mar 2017 08:47:50 +0000 (00:47 -0800)
commitf247addc55ecf9e35dbd1afd8c8da044bef7a3c3
treeaa16ad0b17ccb64f76594bf87392510d08ff8a80
parent9407546428fd44e96a457c67fe81b568e724911b
CRM-20224 - Civi\API\Events - Rename internal events (`api.foo` vs `civi.api.foo`)

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 `api.foo` convention.  Based on
grepping universe, I don't believe any extensions rely on the `DAO::*`
events.
Civi/API/Events.php
Civi/API/Subscriber/WrapperAdapter.php