{"push_id":739633851,"size":2,"distinct_size":2,"ref":"refs/heads/4.6-sched-ref","head":"0767aff70d86158d9793637bd2ee533f7b4fa229","before":"821da425dfa1b5546170402f73351a589dcc68ae","commits":[{"sha":"db89314b63f4f65295c984976164c3a668c3a5b5","author":{"email":"2a56db891c70907901517a1f205658772720d3f5@civicrm.org","name":"Tim Otten"},"message":"CRM-13244 - ActionSchedule - Extract entity-specific logic for tokens and dropdowns.\n\nThe `ActionSchedule` BAO had a ton of duplicate, helter-skelter code for\nlooking up specific details about specific entities and mappings.  The\nmapping class (`CRM_Core_DAO_ActionMapping`) had an anemic model.  The\nmapping records could be modified in the DB, but in practice this was\npointless because they depended on so many hard-coded lookups.  And there\nwere some confusing variable names (sel1, sel2, sel3, etc) and\nvariable-shuffling.\n\nThis revision moves several entity-specific bits into new classes\n(`Civi\\ActionSchedule\\Mapping` and `CRM_Core_ActionScheduleTmp`), abandons\nthe pretense of DB editing, centralizes mapping-related lookups, and replaces\nvarious references to `CRM_Core_DAO_ActionMapping`.\n\nThis is envisioned as an intermediate step; the two classes are still a bit\nheavy (mixing together logic for unrelated entities) and should be split\nfurther.","distinct":true,"url":"https://api.github.com/repos/totten/civicrm-core/commits/db89314b63f4f65295c984976164c3a668c3a5b5"},{"sha":"0767aff70d86158d9793637bd2ee533f7b4fa229","author":{"email":"2a56db891c70907901517a1f205658772720d3f5@civicrm.org","name":"Tim Otten"},"message":"WIP - prepareMailingQuery","distinct":true,"url":"https://api.github.com/repos/totten/civicrm-core/commits/0767aff70d86158d9793637bd2ee533f7b4fa229"}]}