epriestley 522e5b4779 Build an event dispatch mechanism into Phabricator ... Summary: This is an attempt to satisfy a lot of the one-off requests a little more generally, by providing a relatively generic piece of event architecture. Allow the registation of event listeners which can react to various application events (currently, task editing). I'll doc this a bit better but I wanted to see if anyone had massive objections to doing this or the broad approach. The specific problem I want to address is that one client wants to do a bunch of routing for tasks via email, so it's either build a hook, or have them override most of ManiphestReplyHandler, or something slightly more general like this. Test Plan: Wrote a silly listener that adds "Quack!" to a task every time it is edited and edited some tasks. I was justly rewarded. Reviewers: nh, jungejason, tuomaspelkonen, aran Reviewed By: aran CC: aran, epriestley Differential Revision: 881		2011-09-30 12:16:40 -07:00
..
configuration	Provide more thorough defaults in the configuration guide template	2011-09-14 09:52:19 -07:00
contributing	Organize, update, and improve some documentation.	2011-06-25 20:33:25 -07:00
developer	Update doc example.	2011-08-03 09:16:50 -07:00
flavortext	Document mercurial and immutable history doctrines	2011-09-15 07:45:22 -07:00
technical	Allow Phabricator storage engines to be extended and configured	2011-07-21 16:44:24 -07:00
userguide	Build an event dispatch mechanism into Phabricator	2011-09-30 12:16:40 -07:00
installation_guide.diviner	Provide a basic update script for Phabricator	2011-06-29 20:05:28 -07:00
introduction.diviner	Organize, update, and improve some documentation.	2011-06-25 20:33:25 -07:00
roadmap.diviner	Some documentation updates.	2011-09-14 08:02:31 -07:00