consumption tracking

[jvanasco]

I've been playing around with 'consumption tracking' of ashes templates for a while, but haven't figured out a good approach yet. I figured I should post here and perhaps someone else has been working on this task as well...

What I would like to accomplish: tracking what objects/assets are accessed/consumed in our templates via ashes. We render in ashes and dust, so this would allow for passing the data structure for a given template through a "sieve" when rendering any templates client-side (i.e. Ashes can potentially reduce a 100k json payload to the 15k that will be used) and also help tailor the data population.

I originally tried to do this via the data objects passed in to ashes, but that can't handle alternate logic comparisons.

I imagine I can't be alone in having tried to optimize this bit... right?