epriestley 954831f533 Separate chart functions into a class tree ... Summary: Depends on D20440. Ref T13279. Create a class to represent a chartable function: something we can get some data points out of. Then, make the chart chart two functions. For now, the only supported function is "fact(key)", which pulls data from the Facts ETL pipeline, identified by "key", and takes no other arguments. In future changes, I plan to support things like "fact(tasks.open.project, PHID-PROJ-xyz)", "constant(1000)" (e.g. to draw a goal line), "sum(fact(...), fact(...))" (to combine data from several projects), and so on. The UI may not expose this level of power for a while (or maybe ever) but until we get close enough to the UI that these features are a ton of extra work I'm going to try to keep things fairly flexible/modular. Test Plan: {F6382286} Reviewers: amckinley Reviewed By: amckinley Subscribers: yelirekim Maniphest Tasks: T13279 Differential Revision: https://secure.phabricator.com/D20441		2019-04-18 13:05:52 -07:00
..
application	Fetch chart data via async request and redraw charts when the window is resized	2019-04-18 07:10:05 -07:00
controller	Separate chart functions into a class tree	2019-04-18 13:05:52 -07:00
daemon	Update PhabricatorLiskDAO::chunkSQL() for new %Q semantics	2018-11-13 08:59:18 -08:00
engine	Fix some of the most obvious bugs in fact generation from Maniphest tasks	2018-02-19 12:07:28 -08:00
extract	Remove all application callers to "putInSet()"	2018-12-12 16:41:12 -08:00
fact	Extract count/point data from tasks in Fact engines	2018-02-19 12:06:03 -08:00
function	Separate chart functions into a class tree	2019-04-18 13:05:52 -07:00
management	Make Facts more modern, DRY, and dimensional	2018-02-19 12:05:19 -08:00
query	Continue cleaning up queries in the wake of changes to "%Q"	2018-11-16 12:49:44 -08:00
storage	Fix negative chart values, add storage for charts	2019-04-18 06:59:41 -07:00