Asset dependencies about zf2-assetic-module HOT 8 OPEN

Hi, please try to move b_css up and a_css down.

from zf2-assetic-module.

Yes that will work in this specific case. However, in some cases it is highly undesirable to switch positions any time an asset cannot be found. In fact, I can even produce a case for which switching positions will never work. Therefore we should strive for a fix so that these dependent assets are resolved when possible (i.e. when no circular dependencies exist).

from zf2-assetic-module.

Ok, I'll look closer on this issue.

from zf2-assetic-module.

Is this something that we can tackle in this library; or is this something we should do in Assetic?

from zf2-assetic-module.

This should be done in this library.

from zf2-assetic-module.

Like a wrapper around the colletion with some meta-data (alias, dependencies, inline- or headScript). The Wrapper must be created by a configurable factory. The wrapper can by extended or a implements a pattern to append some functions.

The service builds the dependencies and the StrategyViewhelper solves the order of the collections.

So it would by easy to extend the StrategyViewhelper to create a RequireJS-Config or other async javascript inclusion.

from zf2-assetic-module.

The fact that assets can combine other assets like that is a cool feature and should be documented. It's not entirely clear to me how that work/what else can I do with that. I.e. with 'debug' => true, 'combine' => false, 'buildOnRequest' => true what would the name of the partial asset b be called? As far as I can see it's something like asset name + partX so the output name is somehow lost there.

from zf2-assetic-module.

Hi, I've written a quick and dirty proof of concept dependency resolution that works for us. Can anyone look and tell me if I've taken the right direction?
I will write the clean version with tests then

see: elninocz@3b367f4

from zf2-assetic-module.