Roberto Wesley Overdijk

@diemuzi Sorry I completely missed this one. Is this still a problem?

Hey :) If this is a real issue with Assetic I think you should post your issue there.

Why won't you just name the file `myfile.xx.xx.xx.js`? Anyway, that's a valid question. You could rewrite the path before it hits AssetManager, using the same logic as your rewrite rule.

So if I understand this correctly... You want to load all assets individually for development, and combine them in a collection for production? If so, that's not really possible right...

@dronchik The view helper would basically extend the default headScript helper. You'd be able to configure it (local config) and have it add all files in a collection individually. I'm...

@mael-lg I'm not entirely sure what you're asking. @sokac is the main author of the cache warmup, so perhaps he'll be able to answer your question.

Some ideas: - View helper could force internal lookup - View helper forcing lookup would mean there's cache busting (based on file contents) - Pushing to CDN could be done...

@work-out-web I see your problem. It's not a "risk", it's just too much freedom; and you're right. What we could do is add a config key for restrictions (essentially blacklisting...

@work-out-web We don't want to avoid BC, we want to avoid BC-breaks. If we add white/black-listing it has to be for dirs, paths, and aliases. While on that, we might...

I guess it has. Though we actually bundle our assets ourselves, and prefer them to be accessible to the public (in case we need a file for a specific component...